Closed Bug 1518434 Opened 5 years ago Closed 5 years ago

Custom element is broken, and flag state is wrong

Categories

(Core :: DOM: Core & HTML, defect, P3)

64 Branch
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox64 --- affected
firefox65 --- affected
firefox66 --- affected

People

(Reporter: sandy.morphis, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce:

Created custom element and transpiled into es5 and provided required polyfills.
I was working till version 62 on Firefox.

Actual results:

Updated to version 64 and its stoped working now. looked into flags 'dom.webcomponents.customelements.enabled' it is enabled by default. No mention of this change in change log. If I disable this flag everything works.

Expected results:

Custom elements must have worked with provided polyfill. And flag 'dom.webcomponents.customelements.enabled' must have been false.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:64.0) Gecko/20100101 Firefox/64.0
Build ID: 20190108160530

I managed to reproduce this issue on macOS 10.13.6 with the latest Firefox release version 64.0.2. The issue also occurs on the latest Beta and Nightly builds.

Status: UNCONFIRMED → NEW
Component: Untriaged → DOM
Ever confirmed: true
OS: Unspecified → All
Product: Firefox → Core
Hardware: Unspecified → All

Edgar may help us understand what's up there.

Flags: needinfo?(echen)

I tried attachment #9034964 [details], I don't see anything abnormal.
I also tried it on Google Chrome, I don't see any difference, either.
I am not sure what is this issue about. Could you provide a minimal test case to reproduce the issue?

Flags: needinfo?(echen) → needinfo?(sandy.morphis)

Cristian, it seems you could reproduce the issue, but I am not sure what is this issue about. Could you provide more detailed information? Thanks

Flags: needinfo?(george.craciun)

Steps to reproduce:

  1. Open the index file from the attachment
  2. Click several times on the "Add point to chart!" button
  3. Notice that some lines from the graphic are broken

Note1: Hover the mouse cursor over the lines and the broken ones are fixed.
Note2: This issue is not reproducible on Chrome.

Flags: needinfo?(george.craciun)

Hi,

Just a reminder that even if we don't look at demo and just see flags "dom.webcomponents.customelements.enabled" status, it is set to "true" which must be false because firefox note release custom element support officially.

Thanks

Flags: needinfo?(sandy.morphis)

(In reply to sandy.morphis from comment #6)

firefox note release custom element support officially.

Please see https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/63#APIs. Thanks.

Priority: -- → P3

(In reply to Cristian Craciun from comment #5)

Steps to reproduce:

  1. Open the index file from the attachment
  2. Click several times on the "Add point to chart!" button
  3. Notice that some lines from the graphic are broken

Note1: Hover the mouse cursor over the lines and the broken ones are fixed.
Note2: This issue is not reproducible on Chrome.

I could also reproduce with STR now. Thanks.

(In reply to Edgar Chen [:edgar] from comment #7)

(In reply to sandy.morphis from comment #6)

firefox note release custom element support officially.

Please see https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/63#APIs. Thanks.

Ok My bad. I tried to find but missed it.

Thanks @Edgar

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: