This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18299 - Please explain how hidden=true interacts with plugin loading. Should it be treated as display:none?
Summary: Please explain how hidden=true interacts with plugin loading. Should it be t...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 18:00 UTC by contributor
Modified: 2012-10-21 22:26 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2012-07-18 18:00:40 UTC
This was was cloned from bug 15133 as part of operation convergence.
Originally filed: 2011-12-09 23:19:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2011-12-09 23:19:46 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html
Multipage: http://www.whatwg.org/C#the-hidden-attribute
Complete: http://www.whatwg.org/c#the-hidden-attribute

Comment:
Please explain how hidden=true interacts with plugin loading.  Should it be
treated as display:none?

Posted from: 173.164.128.209
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.0 Safari/535.11
================================================================================
 #1   Eric Seidel                                     2011-12-09 23:23:15 +0000 
--------------------------------------------------------------------------------
See https://bugs.webkit.org/show_bug.cgi?id=56575 for context on how WebKit currently has trouble with hidden=true plugins, since we need to not load display:none plugins:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-November/033732.html
but at least that author expects hidden=true to not act like display: none.
================================================================================
 #2   Ian 'Hixie' Hickson                             2012-01-31 22:55:54 +0000 
--------------------------------------------------------------------------------
Well first, hidden=true is bogus. hidden="" is a boolean attribute, meaning it's either present or absent, and its value, if any, has to be the same as its name.

But that's irrelevant here since this is a legacy page, not a page using the new hidden="" attribute.

If we have to address this, I propose doing it by changing the [hidden] rule in ua.css to:

   [hidden]:not(object):not(embed), ... { }

   object[hidden], embed[hidden] { width: 0; height: 0; }
   object[hidden] { overflow: hidden; }

...in the ua.css file.
================================================================================
Comment 1 Edward O'Connor 2012-10-12 17:59:38 UTC
Silvia, this has been fixed in WHATWG r7453.
Comment 2 Silvia Pfeiffer 2012-10-21 22:26:28 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-v2.html

Status: Accepted

Change Description:
https://github.com/w3c/html/commit/a6d060f1109bb8b715ef54002a9cb7344ee4a592

Rationale: Adopted WHATWG patch