[chromium-discuss] Chrome anchor tag target attribute behavior has changed between 66 and 67

[j***@minutekey.com]

This issue occurs in windows as well.

We have two internal websites, call them A and B, one for tickets and one
for management. Various pages on these sites link back to the other site
and use `target="A"` and `target="B"` in the links so that users don't end
up with dozens of tabs open. It appears that this changed in between 66 and
67, now when users click on one of these links, if a tab of that target is
already opens, it reloads that tab but does not switch to it.

To reproduce:
1) Site "A" is open, users click a link with `target="B"`.
2) A new tab is opened and chrome switches to that tab.
3) The user clicks a link on site "B" that has `target="A"`.

Behavior in 67:
4) The existing site "A" tab reloads in the background and chrome *does
not* switch to that tab.
5) The user now has to switch to the site "A" tab manually.

Behavior in 66 (what we want to happen):
4) Chrome switches to the site "A" tab and loads the link the user had
clicked on.

Is there anything we can do to our anchor tags to get the old behavior?
Is there anything our internal users can do to get the old behavior back?
Is this a bug that can/will be fixed?

Thanks!

[PhistucK]

Something tells me that this is an intentional change to break pop-unders
or tab-unders, but it might be either unrelated to pop-unders or
tab-unders, or completely unintentional.

You can search crbug.com for an existing issue and star it. If you cannot
find one, file a new issue using the "New issue" link on the same page.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment.
It just wastes the time of Chrome engineers and sends unnecessary e-mails
to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get
triaged (and fixed) faster.

Thank you.


☆*PhistucK*

Post by j***@minutekey.com
This issue occurs in windows as well.
We have two internal websites, call them A and B, one for tickets and one
for management. Various pages on these sites link back to the other site
and use `target="A"` and `target="B"` in the links so that users don't end
up with dozens of tabs open. It appears that this changed in between 66 and
67, now when users click on one of these links, if a tab of that target is
already opens, it reloads that tab but does not switch to it.
1) Site "A" is open, users click a link with `target="B"`.
2) A new tab is opened and chrome switches to that tab.
3) The user clicks a link on site "B" that has `target="A"`.
4) The existing site "A" tab reloads in the background and chrome *does
not* switch to that tab.
5) The user now has to switch to the site "A" tab manually.
4) Chrome switches to the site "A" tab and loads the link the user had
clicked on.
Is there anything we can do to our anchor tags to get the old behavior?
Is there anything our internal users can do to get the old behavior back?
Is this a bug that can/will be fixed?
Thanks!
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss
---
You received this message because you are subscribed to the Google Groups
"Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Jacob Brouwer]

I couldn't find an existing bug, so I filed one here:
https://bugs.chromium.org/p/chromium/issues/detail?id=856779&can=2&q=target%20anchor&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

Thanks!

Post by PhistucK
Something tells me that this is an intentional change to break pop-unders
or tab-unders, but it might be either unrelated to pop-unders or
tab-unders, or completely unintentional.
You can search crbug.com for an existing issue and star it. If you cannot
find one, file a new issue using the "New issue" link on the same page.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment.
It just wastes the time of Chrome engineers and sends unnecessary e-mails
to all of the people who starred the issue.
You can reply with a link to the found or created issue and might get
triaged (and fixed) faster.
Thank you.
☆*PhistucK*

Post by j***@minutekey.com
This issue occurs in windows as well.
We have two internal websites, call them A and B, one for tickets and one
for management. Various pages on these sites link back to the other site
and use `target="A"` and `target="B"` in the links so that users don't end
up with dozens of tabs open. It appears that this changed in between 66 and
67, now when users click on one of these links, if a tab of that target is
already opens, it reloads that tab but does not switch to it.
1) Site "A" is open, users click a link with `target="B"`.
2) A new tab is opened and chrome switches to that tab.
3) The user clicks a link on site "B" that has `target="A"`.
4) The existing site "A" tab reloads in the background and chrome *does
not* switch to that tab.
5) The user now has to switch to the site "A" tab manually.
4) Chrome switches to the site "A" tab and loads the link the user had
clicked on.
Is there anything we can do to our anchor tags to get the old behavior?
Is there anything our internal users can do to get the old behavior back?
Is this a bug that can/will be fixed?
Thanks!
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss
---
You received this message because you are subscribed to the Google Groups
"Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an