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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13926

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-11 23:13:33 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: Fixed the first thing.

I've left the second thing as is. I agree it doesn't strictly match all UAs,
and I wouldn't recommend to those UAs that they rush to match the spec.
However, given that <frameset> rendering really doesn't match CSS rendering
anyway, I think it's fine that the check for this would happen at the top level
(meaning UAs don't have to load up the CSS machinery only to render a single
thing that doesn't follow CSS anyway), rather than having it just be special
rendering for <frameset> that then is itself laid out using CSS. In theory it
makes the model a little simpler.

-- 
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 Tuesday, 11 October 2011 23:13:35 UTC