New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 847415 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-06-11
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Links within STYLEPOINT fail on CHROMIUM but work on Firefox

Reported by comer.ed...@gmail.com, May 29 2018

Issue description

Chrome Version       : Version 66.0.3359.181 (Official Build) Arch Linux (64-bit)
URLs (if applicable) : https://google.github.io/styleguide/shell.xml?mc_cid=2498c2fa19&mc_eid=5ec9af561f
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox: 60.0.1 (64 bit)
       Edge:

What steps will reproduce the problem?
(1) Click on right-arrow buttons. Chromium=nothing. Firefox=Opens link
(2)
(3)

What is the expected result?


What happens instead?


Please provide any additional information below. Attach a screenshot if
possible.

 
Expected result is opening of link,
But nothing happens

Comment 2 by e...@chromium.org, May 29 2018

Components: Blink>HitTesting
Labels: Needs-Feedback
Are you talking about the ▶⃞ symbol? Clicking that expands the section for me in both firefox and chrome.
Yes, he ▶⃞ symbol? For my Chromium version it does nothing but works fine
in Firefox (Version 66.0.3359.181 (Official Build) Arch Linux (64-bit))
Project Member

Comment 4 by sheriffbot@chromium.org, May 29 2018

Cc: e...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Yes, the ▶⃞ symbol. For my Version 66.0.3359.181 (Official Build) Arch Linux (64-bit) it does nothing but works correctly in Firefox
Labels: Needs-Feedback
NextAction: 2018-06-11
Could you wait a couple of days (hopefully) and see if this reproduces in M-67. Or try Canary.

We haven't reproduced it yet, but I am using M-67.
Labels: Needs-Triage-M66
I installed Version 67.0.3396.62 (Official Build) (64-bit) and it works correctly.

Project Member

Comment 9 by sheriffbot@chromium.org, May 30 2018

Cc: schenney@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
In summary:
Chrome Version 67.0.3396.62 (Official Build) (64-bit) works correctly.
Chromium Version 66.0.3359.181 (Official Build) Arch Linux (64-bit) fails as described above.
Labels: Needs-Feedback Triaged-ET
@Reporter: As per comment# 8, the issue is not reproducible on latest chrome stable version# 67.0.3396.62, could you please provide your confirmation on closing the issue.

Thanks!
While bug is fixed in Chrome v67 it remains in current Chromium v66. The Chromium release schedule for v67 was May 29th, 2018 but has not yet been propagated to the repository. Once I have installed Chromium v67 verified that the bug is fixed in Chromium v67 I will close the issue.
Project Member

Comment 13 by sheriffbot@chromium.org, May 31 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
As per comment #12, adding Needs-Feedback label.

Thanks...!!
Just upgraded chromium to - Version 67.0.3396.62 (Official Build) Arch Linux (64-bit) and problem remains as before.
Project Member

Comment 16 by sheriffbot@chromium.org, Jun 3 2018

Cc: krajshree@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback OS-Linux
We can't reproduce this, which leaves us asking you lots of questions to try to narrow it down.

Is it possible to change fonts to see if this is an issue with the font box information?

Do you have any non-default scaling or zoom applied?

Do you have access to any other machines to see if it specific to a particular computer?
Is it possible to change fonts to see if this is an issue with the font box information?
- I changed fonts to URW Bookman - no change

Do you have any non-default scaling or zoom applied?
- No - Page zoom is 100%

Do you have access to any other machines to see if it specific to a particular computer?
- I have a laptop which will soon be updated to v65 Chromium (latest there is on that release) and I'll test, once updates finish, and post result.
- On this desktop machine, I currently have Firefox (60.0.1 (64-bit)), Chromium (Version 67.0.3396.62 (Official Build) Arch Linux (64-bit)) and Chrome Version (Version 67.0.3396.62 (Official Build) (64-bit)) installed. The link below is to a screenshot of all three browsers on the same page, for comparison. I clicked the toggle all summaries icon which opens on Chrome and Firefox but not chromium.
https://i.imgur.com/eFc5c31.png

- My desktop hardware information is at: https://pastebin.com/U08WQcEf




Project Member

Comment 19 by sheriffbot@chromium.org, Jun 4 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
UPDATE: Tested on laptop running Linux Mint 17.1 e/w Chromium 63.0.3282.167 64bit
Works - BUT this is a much older version of Chromium.
Sorry, I failed to process that the issue is with Chromium builds and not Chrome. That's what I get for staring at bug reports all day.

On a tip-of-trunk chromium build I do not see the issue. Where do you get your chromium versions from?
Re: Where do you get your chromium versions from?
- Installed from Manjaro/Arch distribution. It is Chromium (Version 67.0.3396.62 (Official Build) Arch Linux (64-bit)), meaning that it was built by the Arch Linux distribution packagers. Their link is:
https://www.archlinux.org/packages/extra/x86_64/chromium/
Have you filed a bug with Arch Linux? Given this works for us on a trunk build, on a Debian based system, it seems to be specific to the Arch build.
No, I haven't filed a bug with Manjaro/Arch. I will attempt to do so - BUT first I'll ask on the forum if others experience the same problem.
Labels: Needs-Feedback
Waiting for reporters feedback, hence adding Needs-Feedback label.

Thanks!
Project Member

Comment 26 by sheriffbot@chromium.org, Jun 5 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Feedback
As per comment#24 (i.e.,C#25 & C#26) adding the label back.

Thanks!
Another Manjaro user posted a reply that identifies the failure:

If you open the developer tools you’ll see the following error in the console:

shell.xml?mc_cid=2498c2fa19&mc_eid=5ec9af561f:212 Uncaught ReferenceError: ShowHideByName is not defined

    at HTMLSpanElement.onclick (shell.xml?mc_cid=2498c2fa19&mc_eid=5ec9af561f:212)

onclick @ shell.xml?mc_cid=2498c2fa19&mc_eid=5ec9af561f:212

Project Member

Comment 29 by sheriffbot@chromium.org, Jun 6 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: TE-NeedsTriageHelp
comer.edward@ Thanks for the update.

As this issue is not reproducible at TE end, adding 'TE-NeedsTriageHelp' label and requesting someone from Blink>HitTesting team to look into the issue and help in further triaging.

Thanks..
The NextAction date has arrived: 2018-06-11
Status: WontFix (was: Unconfirmed)
shell.xml is not a chromium file. It seems the problem is outside our control. Closing.
shell.xml is imported as part of the stylesheet imported by the offending Google web page. "https://google.github.io/styleguide/shell.xml?mc_cid=2498c2fa19&mc_eid=5ec9af561f"
I filed a bug report with the Google github repository for shell.xml - see: https://github.com/google/styleguide/issues/370




This seemed to be caused by an interaction between the system's libxslt and the bundled libxml. chromium 67.0.3396.87-2 (just released in Arch) switches back to using the system's libxml and this appears to fix the issue.
Isn't it a security issue? Fedora is affected.

Version 67.0.3396.79 (Developer Build) Fedora Project (64-bit)

Fixed in Version 67.0.3396.87 (Official Build) Manjaro Linux (64-bit)

Sign in to add a comment