Closed
Bug 975653
Opened 11 years ago
Closed 11 years ago
chromestatus.com's Stack Rank and Timeline metrics views work in Chrome but not Firefox
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INVALID
People
(Reporter: cpeterson, Unassigned)
References
()
Details
This Chrome site uses Polymer.
STR:
1. Load http://www.chromestatus.com/metrics/feature/popularity
2. Wait
RESULT:
The list of feature names never actually loads in Firefox, but it does in Chrome.
STR:
1. Load http://www.chromestatus.com/metrics/feature/timeline/popularity
2. Click on the "Select a property" drop-down list
RESULT:
The drop-down list is empty in Firefox, but not Chrome.
Comment 1•11 years ago
|
||
Is this a regression?
And if not, is this just a Polymer bug?
Keywords: qawanted,
testcase-wanted
Reporter | ||
Comment 2•11 years ago
|
||
This is not a Firefox regression. The site fails to work in Nightly 30, Firefox 27, and ESR 24.
Comment 3•11 years ago
|
||
It also completely fails to work in IE9, and in IE10/11 seems to get the data but the rendering is totally wrong, afaict...
I'm willing to be convinced this is other than the site just relying on non-standard behavior, but would need some more data.
Reporter | ||
Comment 4•11 years ago
|
||
If this site does not work in IE, then it's probably a Polymer or Chromium Dashboard problem. I will just report the problem on their issue tracker:
https://github.com/GoogleChrome/chromium-dashboard
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 5•11 years ago
|
||
Reporter | ||
Comment 6•11 years ago
|
||
The resolution of this problem [1] was that chromestatus.com's dashboard had a property name conflict with Firefox's HTML Microdata API property `properties`. Bug 909633 proposes to remove the HTML Microdata API (as WebKit and Blink have done).
[1] https://github.com/GoogleChrome/chromium-dashboard/commit/24a0a8edaa2eadf274b15b3e76bc5349364e478e
Keywords: qawanted,
testcase-wanted
Comment 7•11 years ago
|
||
FWIW, this works correctly now (presumably because the github issue in comment 5 has been closed).
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•