W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13926] The definition of when a frameset element is special doesn't make sense

From: <bugzilla@jessica.w3.org>
Date: Sat, 27 Aug 2011 05:27:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QxBR1-0006tO-Ds@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13926

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> 2011-08-27 05:27:58 UTC ---
In particular, the current draft says that the special rendering should take
place "When an html element's second child element is a frameset element".

But what if the first child element is a <body> element?

It would make a bit more sense to do the special stuff for frameset only if the
frameset is the "body element" of the document.  But even then, you get into
trouble in situations like this (as XHTML):

  <!DOCTYPE html>
  <span/>
  <frameset><!-- Stuff here --></frameset>

Or even this (as HTML):

  <!DOCTYLE html>
  <head>
    <style>
      head, style { display: block; }
    </style>
  </head>
  <frameset><!-- stuff here --></frameset>

What do UAs do with this stuff right now?  How can we define this to actually
make sense?

For what it's worth, on that last example both Gecko and WebKit seem to render
the line of text, then the frameset as normal...

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 27 August 2011 05:28:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC