Closed
Bug 1052150
Opened 10 years ago
Closed 7 years ago
dom.webcomponents.enabled should be false for non certified apps until the spec is 100% implemented
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sole, Unassigned)
References
Details
We suspect it is set to true in the current 2.0 and 2.1 simulators, and they are breaking our code built with "the web components standard" because the platform.js polyfill is convinced there *is* support for web components, when it's not actually working because it's an incomplete implementation. This will break any other code that uses plain Vanilla JS components + possibly platform.js
Reporter | ||
Updated•10 years ago
|
Blocks: gaia-web-components
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Blocks: gaia-web-components
Comment 1•10 years ago
|
||
There is a fix for this issue here: https://bugzilla.mozilla.org/show_bug.cgi?id=1038439#c12 It still needs to be upstreamed to v2.0
Comment 2•10 years ago
|
||
Is this bug already greenlit for upstreaming, or is there a nomination process?
Comment 3•10 years ago
|
||
(In reply to Potch [:potch] from comment #2) > Is this bug already greenlit for upstreaming, or is there a nomination > process? Nevermind, I see the uplift approval has already gone through. Thanks!
Comment 4•10 years ago
|
||
Update on this? Is 2.0 going to land with this as is or is it getting turned off by default? and what's the target release for 2.0?
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•