We started discussing the spec as a way for pages to figure out how they were embedded in the browser: foreground tab, background tab etc. I dont think we should implement the display:none case because, - Keeping the spec simple - ensures that the spec is implemented consistently. The more complicated we make the spec, we may see vendors diverge from it. - The discussion to include some cases - such as display:none and not others like visibility:hidden, or pages hidden by window seem a bit arbitrary to me. Like I mentioned this was also not the intended use of the initial spec (ofcourse that can change). Thanks Shishir On Fri, Oct 7, 2011 at 2:13 PM, Jonas Sicking <jonas@sicking.cc> wrote: > On Fri, Oct 7, 2011 at 11:26 AM, Shishir Agrawal <shishir@chromium.org> > wrote: > > If we want to include display none, why not consider other visibility > cases > > - All of which would probably benefit web developers. I think the idea > was > > to keep the page visibility consistent and simple. > > Simpler for who? The web developer or the person implementing the spec? > > So far no-one has been able to argue why this is better for the web > developer. As far as I can see it's strictly worse for them. > > I'm certainly open to adding other visibility cases. Anne brought up > visibility:hidden which I would be ok with, though as I explained > there are arguments against it. > > / Jonas >
Received on Monday, 10 October 2011 17:27:35 UTC