This bug entered during discussion at [PP] bug triage today. See Bugzilla #1981.

There is not a good answer. Basically, the answer is to use CSS-P. layers were non-standard, and devedge has been discouraging their use for almost a year now. Additionally, not many pages using layers have been deployed on the Internet. All that said, the LAYER tag will work (works today), just not the Layer DOM or <LAYER SRC="foo.html"> style transclusion.

Adding johng to cc/

Adding johng to cc list

Our layer path migration strategy was decided months ago: We will release a beta that does not support the Layer DOM APIs but does support the LAYER tag in HTML, with the exception of the SRC attribute. Note that all of the absolute positioning and z-ordering functionality of the LAYER tag is achievable using CSS2 properties that NGLayout supports today. For the past year, DevEdge has been encouraging developers to use the CSS properties instead of the HTML tag. I've met with most of the major content developers using the layer tag today (there are only a handful) and all of them are very excited about the new API (which happens to work in *both* browsers) and don't care that their old LAYERs stuff will need to be migrated. Nonetheless, if there is significant developer backlash to the first beta which doesn't contain the LAYER DOM APIs, then we can revisit the issue for a 5.01 point release or later beta at that time. Troy, Vidur, RickG own this on the engineering side. On the marketing side, byunn and I helped craft this plan with the eng leads mentioned and joki.

Marking as Verified/Won't Fix. cc'ing chofmann as FYI.