You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugIndicates an unexpected problem or unintended behavior.p1We will address this soon and will provide capacity from our team for it in the next few releases.
I think there are a couple of options, and I'd welcome opinions!
(1) have <div class="output"> wrapping the shadow DOM contents.
(2) make examples include the container element explicitly in the HTML pane.
The advantages of (1) are that existing examples don't need to change, and (more importantly IMO) we keep the HTML pane contents more narrowly focused on the example being demonstrated
The advantage of (2) is that there is less magic: it's clear what .output in the CSS pane refers to.
I think I'd vote for (1), to keep the HTML pane contents minimal. I think .output is pretty obvious.
schalkneethling
added
bug
Indicates an unexpected problem or unintended behavior.
p1
We will address this soon and will provide capacity from our team for it in the next few releases.
labels
May 10, 2018
bugIndicates an unexpected problem or unintended behavior.p1We will address this soon and will provide capacity from our team for it in the next few releases.
It seems like using
.output
in the CSS tab doesn't work anymore now that we're using Shadow DOM.I see no hamster here, for example:
http://127.0.0.1:9090/pages/tabbed/select.html
CSS: https://github.com/mdn/interactive-examples/blob/master/live-examples/html-examples/forms/css/select.css
The text was updated successfully, but these errors were encountered: