- From: <bugzilla@jessica.w3.org>
- Date: Thu, 16 Apr 2015 16:42:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28446 --- Comment #2 from Dimitri Glazkov <dglazkov@chromium.org> --- >From https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0109.html: "I was asked to provide a use case for our stance. One that we've found with Firefox OS is custom dialogs, quoting Wilson Page: # I have an <x-dialog> component. It takes care of transitioning # in and out of the viewport and appropriate styling contained # elements (<h1>, <button>, <p>). # # I want to be able to extend this component to produce # <x-dialog-alert>. In this case extending the prototype alone # isn't enough, I need to also be able to extend the markup # and styling of <x-dialog>. # # At the point of creation <x-dialog-alert> can add a second # ShadowRoot that allows it to compose its own content # inside that of the 'old' <x-dialog> ShadowRoot. Without this # <x-dialog-alert> would have to duplicate all the markup, style # and interaction code again." -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 16 April 2015 16:42:42 UTC