while testing bug 40458, I noticed that none of the head elements render in Show All Tags mode, they should probably be rendered especially since they render in HTML Source mode.

This is basically impossible to do. If the head elements can't render in normal mode, they can't render in Show All Tags Mode. I think it would take some very serious changes to layout to make this happen. That's unlikely - setting to future.

Charles, I am sorry to strongly disagree with you... The sub-elements in HEAD don't show up in normal mode because normal mode inherits a 'display : none' on these elements. I have tried successfully to change that behavior in AllTags mode and it works just fine... **BUT** before adding that to the build, there are some issues related to the selection and the direct modification of these elements that we should solve. I guess that you can re-assign this bug to me and reasonably set 1.0 as target milestone :-)

-->glazman

But have you tried editing in HEAD region while in this new "All Tags" mode? I think you'll find some suprises. Joe's HTML-insert rules code doesn't let you have a selection outside of the BODY element, so I think this will subvert your efforts. I think your strategy for the new tag labels is excellent, but I don't think we want to include all the attribute information as you show in the <meta> elements. That will really clutter the display, especially after we start using inline CSS style in the content elements. Note that we also loose the subtle difference between "inline" and "block" tags (latter are oriented sideways in current All Tags design, so they take up less horizontal space.) See also bug 76023, which suggests using ":before" to solve display of missing tagnames, such as HR. I think a dependency is a good idea.

yes, I discovered that problem. We have at least two issues to solve : (a) content goes into body even if the caret is somewhere in HEAD ; that should not be too hard to solve IMHO (b) if you move the caret using keyboard arrows, the caret goes *into* generated content ; of course, that is a bug. Probably for Mike. With these two issues solved, I think that we'll have a ground layer for an AllTags mode able to work with any XML DTD, not only HTML :-)

The "force into body" issue is messy. It's deeply ingrained in the rules system. I tried removing that requirement and there were lots of bad side effects. Joe can elaborate. But I think we should tack the problem (next version!)

*** This bug has been marked as a duplicate of 88036 ***

verified.