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 12881 - "is expected to hide it" is a bit vague. Clarify that it means display:none.
Summary: "is expected to hide it" is a bit vague. Clarify that it means display:none.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 13:19 UTC by contributor
Modified: 2011-09-22 23:43 UTC (History)
8 users (show)

See Also:

Attachments

Description contributor 2011-06-03 13:19:28 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/rendering.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#display-types

Comment:
"is expected to hide it" is a bit vague. Clarify that it means display:none.

Posted from: 85.227.154.77 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.8.131 Version/11.11
Comment 1 Michael[tm] Smith 2011-08-04 05:36:06 UTC 
mass-move component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 19:23:56 UTC 
Would "is expected to force its 'display' property to compute to 'none'" be ok? Or should it just be defined as a replaced element with dimensions 0x0?
Comment 3 L. David Baron (Mozilla) 2011-08-10 19:54:05 UTC 
Well, our UA style sheet has:

audio:not([controls]) {
  display: none;
}

It's not clear to me why it needs to be magical and non-overridable, but display:none sounds fine.
Comment 4 Simon Pieters 2011-08-11 11:25:45 UTC 
It should be non-overridable because authors may want to style audio as display:block but only expect it to affect audio with controls. It's not even defined what should be rendered when audio without controls when it has display other than none (do you render the fallback? or a zero-dimension replaced element? something else?).
Comment 5 Simon Pieters 2011-08-11 11:26:57 UTC 
(In reply to comment #2)
> Would "is expected to force its 'display' property to compute to 'none'" be ok?

Yes. (Also noscript and maybe other things use that phrase as well.)

> Or should it just be defined as a replaced element with dimensions 0x0?

That's not how it's implemented today.
Comment 6 Ian 'Hixie' Hickson 2011-09-22 23:42:06 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 7 contributor 2011-09-22 23:43:56 UTC 
Checked in as WHATWG revision r6567.
Check-in comment: Better define 'hide' in the rendering section.
http://html5.org/tools/web-apps-tracker?from=6566&to=6567