<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">If we could make relaxing the naming rules based on namespace fast, that does seem like a simpler temporary state than modifying the tag name when creating the element. Then we could still use the rest of the proposed workflow. So, first change nsContentUtils::IsCustomElementName to allow these names in XUL namespace (either using a whitelist of names or by allowing all non-dashed names). Then for each binding:</div><div class=""><br class=""></div><div class="">1) Do the binding to custom element migration and land it.</div><div class="">2) Go through and convert all the tag names to the dashed version, landing the conversions as you go.</div><div class="">3) Add a fatal assert (diagnostic or release as desired) in NS_NewXULElement for when we attempt to create the non-dashed version. Convert anything that this assert turns up.</div><div class="">4) (If we used a whitelist of names in IsCustomElementName) remove the name from the whitelist.</div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 13, 2018, at 1:04 PM, Dave Townsend <<a href="mailto:dtownsend@mozilla.com" class="">dtownsend@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Mon, Mar 12, 2018 at 8:20 PM Boris Zbarsky <<a href="mailto:bzbarsky@mit.edu" class="">bzbarsky@mit.edu</a>> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 3/12/18 5:40 PM, Brian Grinstead wrote:<br class="">
> * It would slow down progress, since we'd need to be rebasing around the entire frontend + tests while migrating a binding.<br class="">
<br class="">
We could add a hack to NS_NewXULElement that maps some tag names to<br class="">
others (and creates a new nodeinfo accordingly). This would be used<br class="">
only on a temporary basis, while migrating a binding. So the workflow<br class="">
would go like this:<br class=""></blockquote><div class=""><br class=""></div><div class="">This is roughly an idea I also had. I was wondering though if that would mean that the element would show up in the inspector with the mapped tag name and whether we'd hit issues with CSS not applying correctly. <br class=""></div></div></div>
_______________________________________________<br class="">firefox-dev mailing list<br class=""><a href="mailto:firefox-dev@mozilla.org" class="">firefox-dev@mozilla.org</a><br class="">https://mail.mozilla.org/listinfo/firefox-dev<br class=""></div></blockquote></div><br class=""></body></html>