Re: [whatwg] Fullscreen
On 10/15/2011 07:27 AM, Anne van Kesteren wrote: I wrote up a draft: http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html Defining when exactly the fullscreen enabled flag is set for Document objects I will leave up to HTML. As well as defining the allowfullscreen attribute. Presumably it should be set for Document objects associated with the top-level browsing context and descendant browsing context as long as their browsing context container has the aforementioned attribute set. If we want to transition from fullscreen when navigating, HTML can define that as well, neatly integrated in the navigation section. The Model section of the Fullscreen specification has an appropriate hook. I have not added the key restrictions given earlier emails. Unfortunately there was not that much feedback on them, but maybe this draft will help on that front! I went with fullscreen rather than full screen as that seemed cleaner and easier to type. I also used enter and exit rather than request and cancel as they seemed somewhat nicer too. I'm less attached to this latter change though. To me enterFullscreen() sounds like something which couldn't fail. requestFullscreen() is closer to what actually happens: script asks UA to go to fullscreen mode, but it may fail if user or UA for some reason denies the request. -Olli
Re: [whatwg] Fullscreen
On Oct 15, 2011, at 2:05 AM, Olli Pettay wrote: On 10/15/2011 07:27 AM, Anne van Kesteren wrote: I went with fullscreen rather than full screen as that seemed cleaner and easier to type. I also used enter and exit rather than request and cancel as they seemed somewhat nicer too. I'm less attached to this latter change though. To me enterFullscreen() sounds like something which couldn't fail. requestFullscreen() is closer to what actually happens: script asks UA to go to fullscreen mode, but it may fail if user or UA for some reason denies the request. I agree. requestFullscreen describes what happens much more accurately. eric
[whatwg] How to render typographic puns in HTML5 -- aside, legend, alt, other?
I know that there are a variety of accessibility things in HTML5. Take a look at this small collection of simple typographic puns, currently rendered in SVG: http://cs.sru.edu/~ddailey/svg/2011/simplePuns.svg I've added title and desc to these in a way to explain the sometimes visual effects to audiences that might not be reached by ordinary assistive technology. The use of the mouse or examination of the source should reveal what I'm up to. Question: how would you folks advise doing this in HTML5. Legend was the thing that came to mind, but it looks as though it's not usable everywhere. Aside seems to have slightly different semantics, since it is not so much an aside as an explanation. Maybe this is where a micro-format is appropriate? regards David
Re: [whatwg] Fullscreen
On Sat, Oct 15, 2011 at 4:05 PM, Eric Carlson eric.carl...@apple.comwrote: I agree. requestFullscreen describes what happens much more accurately. enter seems consistent with the Geolocation API, with methods like getCurrentPosition and watchPosition, not requestCurrentPosition and requestToWatchPosition. In other words, the fact that permission might be required to complete the task isn't baked into the method name. IDBDatabase.createObjectStore is similar; the implementation may ask the user permission, but it's not named requestCreateObjectStore. -- Glenn Maynard
Re: [whatwg] How to render typographic puns in HTML5 -- aside, legend, alt, other?
On Sat, Oct 15, 2011 at 2:26 PM, David Dailey ddai...@zoominternet.net wrote: I know that there are a variety of accessibility things in HTML5. Take a look at this small collection of simple typographic puns, currently rendered in SVG: http://cs.sru.edu/~ddailey/svg/2011/simplePuns.svg I've added title and desc to these in a way to explain the sometimes visual effects to audiences that might not be reached by ordinary assistive technology. The use of the mouse or examination of the source should reveal what I'm up to. Question: how would you folks advise doing this in HTML5. Legend was the thing that came to mind, but it looks as though it's not usable everywhere. Aside seems to have slightly different semantics, since it is not so much an aside as an explanation. Maybe this is where a micro-format is appropriate? figure and figcaption are likely the semantic you're looking for. ~TJ
