- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 May 2015 16:50:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28702 --- Comment #1 from steve faulkner <faulkner.steve@gmail.com> --- (In reply to Sailesh Panchang from comment #0) > In "7.1 The hidden attribute" (W3C Recommendation 28 October 2014 ), refer to > "The hidden attribute must not be used to hide content that could > legitimately be shown in another presentation. > For example, it is incorrect to use hidden to hide panels in a tabbed > dialog, because the tabbed interface is merely a kind of overflow > presentation — one could equally well just show all the form controls in one > big page with a scrollbar". > > How is this different from the "skeletal example, the attribute is used to > hide the Web game's main screen until the user logs in:" > <section id="game" hidden> > ... > </section> > > Just as certain content cannot be made available till one logs in, it may > not be possible or logical functionality-wise to display content of > subsequent tabs in a tabbed dialog because there may be dependencies. > The hidden attribute may be removed programmatically when content is to be > rendered just like display:none may be changed to display:block or the like. > > Please can you clarify why it is not suitable in a tabbed dialog? > Thanks, > Sailesh Panchang > [1] http://www.w3.org/TR/html5/editing.html#the-hidden-attribute Hi Sailesh, I agree with your view on use of hidden for a tabbed dialog, the concept of it not being appropriate was introduced and maintained by a form editor. I will modify the text for this in html 5.1 -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 26 May 2015 16:50:54 UTC