Re: [whatwg] Notifications and service workers

On Mon, Oct 6, 2014 at 9:15 AM, Jonas Sicking wrote: > On Mon, Oct 6, 2014 at 12:05 AM, Andrew Wilson > wrote: > > On Sat, Oct 4, 2014 at 4:42 AM, Jonas Sicking wrote: > >> > >> Another thing we could do here is to simply not address this use case. > >> D

Re: [whatwg] Notifications and service workers

On Sat, Oct 4, 2014 at 4:42 AM, Jonas Sicking wrote: > > Another thing we could do here is to simply not address this use case. > Does gmail for android do the same thing? I wasn't able to reproduce > it though I might have done something wrong. > AFAICT, no - gmail for android doesn't use web not

Re: [whatwg] Notifications and service workers

On Tue, Sep 30, 2014 at 10:15 AM, Jonas Sicking wrote: > > On Sep 30, 2014 12:48 AM, "Andrew Wilson" wrote: > > > > > > > > On Mon, Sep 29, 2014 at 9:14 PM, Jonas Sicking wrote: > >> > >> On Mon, Sep 29, 2014 at 6:09 AM, Andrew Wilson

Re: [whatwg] Notifications and service workers

On Mon, Sep 29, 2014 at 9:14 PM, Jonas Sicking wrote: > On Mon, Sep 29, 2014 at 6:09 AM, Andrew Wilson > wrote: > > OK, looked back into the Gmail code (since it'd been a couple of years > since > > I was really down in that notification code). There are two places

Re: [whatwg] Notifications and service workers

umption that the user has seen this notification. This functionality may be somewhat broken on platforms that auto-close notifications though. On Mon, Sep 29, 2014 at 2:15 PM, Jonas Sicking wrote: > On Mon, Sep 29, 2014 at 4:55 AM, Andrew Wilson > wrote: > > On Mon, Sep 29, 2014 at 1

Re: [whatwg] Notifications and service workers

On Mon, Sep 29, 2014 at 1:40 PM, Jonas Sicking wrote: > On Mon, Sep 29, 2014 at 4:35 AM, Andrew Wilson > wrote: > > I'm sorry, I meant that you can only use the 'data' attribute, if the > data > > you want to associate with the notification is structured-clon

Re: [whatwg] Notifications and service workers

' is structured-cloneable - I'm saying that's not sufficient for many uses. -atw On Mon, Sep 29, 2014 at 12:34 PM, Jonas Sicking wrote: > On Mon, Sep 29, 2014 at 3:10 AM, Andrew Wilson > wrote: > > That only works if 'data' is a structured-cloneable data structure. > > Per spec it is yes. > > / Jonas >

Re: [whatwg] Notifications and service workers

form operations on them. On Mon, Sep 29, 2014 at 11:54 AM, Robert Bîndar wrote: > Sounds exactly like an use case of the 'data' attribute. > > 2014-09-29 12:23 GMT+03:00 Jonas Sicking : > >> On Sun, Sep 28, 2014 at 11:15 PM, Andrew Wilson >> wrote: >&g

Re: [whatwg] Notifications and service workers

. > > I've also added Andrew, who might know some historical reasons for the > events. (Andrew: most of this is in context of persistent notifications.) > > * Life-time of existing notifications. > > Chrome currently treats Web Notifications as "persistent"

Re: [whatwg] Notifications improvements

On Fri, Aug 8, 2014 at 2:48 PM, Peter Beverloo wrote: > Hi Andrew, > > On Wed, Aug 6, 2014 at 12:59 PM, Andrew Wilson wrote: >> >> On Wed, Aug 6, 2014 at 12:48 PM, Anne van Kesteren >> wrote: >> > On Wed, Aug 6, 2014 at 10:08 AM, Andrew Wilson >> >

Re: [whatwg] Notifications improvements

On Wed, Aug 6, 2014 at 12:48 PM, Anne van Kesteren wrote: > On Wed, Aug 6, 2014 at 10:08 AM, Andrew Wilson wrote: >> I understand your concern that is driving this proposal: you don't >> want to provide rich APIs that can't be well implemented on every >> platfor

Re: [whatwg] Notifications improvements

On Tue, Aug 5, 2014 at 11:44 PM, Jonas Sicking wrote: > On Fri, Jul 11, 2014 at 12:57 AM, Andrew Wilson wrote: >> >> On Fri, Jul 11, 2014 at 2:30 AM, Jonas Sicking wrote: >>> >>> On Thu, Jul 10, 2014 at 1:04 AM, Andrew Wilson >>> wrote: >>

Re: [whatwg] Notifications improvements

On Fri, Jul 11, 2014 at 2:30 AM, Jonas Sicking wrote: > On Thu, Jul 10, 2014 at 1:04 AM, Andrew Wilson > wrote: > > > > On Thu, Jul 10, 2014 at 5:44 AM, Jonas Sicking wrote: > >> > >> Hi All, > >> > >> We've on and off discussed var

Re: [whatwg] Notifications improvements

On Thu, Jul 10, 2014 at 5:44 AM, Jonas Sicking wrote: > Hi All, > > We've on and off discussed various features added to notifications. > It'd be great to move forward with some of these improvements. > > I think the most low hanging fruit would be to add the following as > data that can be displ

Re: [whatwg] [Notifications] Notification.hasPermission() instead of Notification.permission

Just out of curiosity, what are we hoping that the use counter will show? I'm presuming that every single app that uses the notification API will make at least some use of Notification.permission, so it mostly seems like it's going to show us how often the Notification APIs *in general* are used in

Re: [whatwg] [notifications][editorial] tweaking the "Activating a notification" window.focus() note

The problem here is that the platform's notification design has no way to understand what the application wants to happen when the user clicks on a notification. As a great example - Gmail uses desktop notifications to notify the user about chat events and new emails. When the user clicks on a cha

Re: [whatwg] onclose events for MessagePort

On Sat, Dec 7, 2013 at 2:22 AM, Ian Hickson wrote: > > On Fri, 11 Oct 2013, Andrew Wilson wrote: > > > > Interesting. Section 5.3.1 of the MessagePort spec > > (BTW, I really recommend using the WHATWG HTML spec rather than the > MessagePort spec, especially the versi

Re: [whatwg] Implementation question about Notifications

On Mon, Nov 18, 2013 at 1:01 PM, Anne van Kesteren wrote: > On Thu, Nov 14, 2013 at 10:45 PM, Andrew Wilson > wrote: > > var n1 = new Notification("title"); > > var n2 = new Notification("title", {icon: "invalid_icon_url"}); > > var n3 =

[whatwg] Implementation question about Notifications

The notification spec (http://notifications.spec.whatwg.org/#api) says that the Notification object has the following readonly attributes: title, dir, lang, body, tag, icon. Let's say I make the following calls: var n1 = new Notification("title"); var n2 = new Notification("title", {icon: "invali

Re: [whatwg] The behaviour of Notification.requestPermission() in Workers

Agreed with Anne - I don't see the value in exposing a non-functional requestPermission(). Certainly on Chrome (which only allows invoking requestPermission in the context of user input to prevent abuse) we would be unlikely to support requestPermission() from workers, at least unless we decide to

Re: [whatwg] onclose events for MessagePort

On Sat, Oct 19, 2013 at 2:26 AM, Jonas Sicking wrote: > > > What I think might work is to say that as long as a "channeldropped" > event listener is registered with a port, that is equivalent to > holding a strong reference to the port. I.e. that prevents the channel > from being GCed. Even if no

Re: [whatwg] onclose events for MessagePort

On Fri, Oct 11, 2013 at 10:18 AM, Anne van Kesteren wrote: > On Fri, Oct 11, 2013 at 9:38 AM, Andrew Wilson > wrote: > > *"or while there exists an event listener on either port for the > > channeldropped event."* > > Once you do that you basically rely on the d

Re: [whatwg] onclose events for MessagePort

On Thu, Oct 10, 2013 at 11:52 PM, Jonas Sicking wrote: > On Thu, Oct 10, 2013 at 8:26 AM, Ehsan Akhgari wrote: > > On Thu, Oct 10, 2013 at 2:58 AM, Jonas Sicking wrote: > >> > >> On Wed, Oct 9, 2013 at 3:06 PM, Ehsan Akhgari > wrote: > >> > OK, so I gave this some thought and I and Olli manage

Re: [whatwg] Possible bug in the way the spec about worker GC behavior

On Thu, Oct 10, 2013 at 5:06 PM, Ehsan Akhgari wrote: > On Thu, Oct 10, 2013 at 7:58 AM, Andrew Wilson wrote: > >> Can you be more specific about what in the spec is incorrect? I guess >> you're saying that Gecko shuts down the worker as soon as the parent >> docum

Re: [whatwg] onclose events for MessagePort

On Thu, Oct 10, 2013 at 5:20 PM, Ehsan Akhgari wrote: > > > Why would they expect that? Storing a reference to a port object on a > parent doesn't change the owner of the port. (I agree that this can be a > bit confusing if authors are not familiar with MessagePorts, but this is > part of the se

Re: [whatwg] Possible bug in the way the spec about worker GC behavior

Can you be more specific about what in the spec is incorrect? I guess you're saying that Gecko shuts down the worker as soon as the parent document is no longer active (when the worker transitions to suspendable), so the worker is generally shutdown before the document is discarded? I think that b

Re: [whatwg] onclose events for MessagePort

On Thu, Oct 10, 2013 at 8:58 AM, Jonas Sicking wrote: > > > I could see the GC case not being solvable. > > But is there a reason that we couldn't also fire the event if the > other side is forcefully terminated through a navigation or a > Worker.terminate() call? > I still have the concerns I ex

Re: [whatwg] onclose events for MessagePort

On Tue, Oct 1, 2013 at 7:01 PM, Olli Pettay wrote: > > > I don't understand what "the lifetime of MessagePorts to the lifetime of > their owner document" > means in case of workers. And we sure want to delete MessagePort objects > if nothing from JS side > is keeping it, or the port it is connecte

Re: [whatwg] Notifications: usage feedback

So, I'm not entirely sure how many lessons taken from the FirefoxOS implementation are applicable to the API for web pages in general, but I agree that "what do we do if the user clicks on a notification after the parent page has been closed" is a bit of an unsolved/unsolveable problem with the cur

Re: [whatwg] Navigation and history traversal issues

w a SecurityError). It's rather awkward to test this, but can we have something in the spec to prevent cross-origin history traversal? If this is not in the same section as the "traverse the history by a delta" algorithm can we have a note to say that this can never happen cross-origin? Thanks -- Andrew Oakley

[whatwg] Session history and discarding of Documents

no requirement to maintain session history for any nested browsing context that belongs to a document which is not active but the major browser do. Thanks -- Andrew Oakley -- Andrew Oakley

Re: [whatwg] Notifications: in workers

On Thu, May 16, 2013 at 5:45 PM, Anne van Kesteren wrote: > On Wed, May 15, 2013 at 8:24 AM, Andrew Wilson > wrote: > > On Tue, May 14, 2013 at 9:19 PM, Anne van Kesteren > wrote: > >> Chrome currently does not seem to do any of this particularly well, > >>

Re: [whatwg] Notifications: in workers

On Tue, May 14, 2013 at 9:19 PM, Anne van Kesteren wrote: > On Tue, May 14, 2013 at 8:51 AM, Andrew Wilson > wrote: > > On Sun, Mar 31, 2013 at 4:40 PM, Anne van Kesteren > wrote: > >> This seems problematic for shared workers as it is not clear which > >> win

Re: [whatwg] Notifications: in workers

Sorry, missed this the first time through: On Sun, Mar 31, 2013 at 4:40 PM, Anne van Kesteren wrote: > There is some interest in exposing Notification objects in a worker so > creating one does not require a postMessage() roundtrip. > > This seems problematic for shared workers as it is not cle

Re: [whatwg] suggestions for the Notifications API (http://notifications.spec.whatwg.org/)

On Fri, May 3, 2013 at 6:49 PM, Nils Dagsson Moskopp < n...@dieweltistgarnichtso.net> wrote: > alonn schrieb am Fri, 3 May 2013 18:50:36 +0300: > > > 1. Having a way to check for the current permission without > > initiating a new Notification object first. something like webkit has > > (I'm not

Re: [whatwg] Why do we have and ?

> Hi, > > In my war against useless input types, I had a look at 'month' and > 'week' and I am wondering what was the rationale behind having them in > the HTML specifications. > > Regarding 'month', I mostly don't understand the use case. I can't find > any situation where I am asked to input a

[whatwg] SecurityError with parent, top, window, self and opener members of Window

what the browsers actually do. I can't see any reason why we can't allow access to these properties, should they be in the list of exceptions in section 6.2.1? Are there any more properties that should be in the list? -- Andrew Oakley

Re: [whatwg] Declarative web worker creation and communication?

On Tue, Nov 6, 2012 at 2:21 AM, Fred Andrews wrote: > Hi Andrew, > > Thank you for the feedback. The PUA 'shared context' will likely need to > be a > distinct web worker variant to cater for any required restrictions and > also to > ensure it does not entangle

Re: [whatwg] Declarative web worker creation and communication?

On Mon, Nov 5, 2012 at 10:24 AM, Fred Andrews wrote: > Hi Simon, > > The use I have in mind is a work-in-progress, see: > http://www.w3.org/community/pua/wiki/Draft#Examples > > However the HTML standard already permits a UA to disable JS, and there is > the iframe sandbox, or CSP, or browser ext

Re: [whatwg] Firing canplaythrough when caches/buffers are full

s canplaythrough logic (which admittedly needs a little work) has similar behaviour. I agree it'd be good to formalize the behaviour. Rob: when you say to suspend a download indefinitely would this coincide with dropping the networkState to NETWORK_IDLE and subsequently firing a suspend event? Andrew

[whatwg] Image cache behaviour

I've noticed that some browsers (Firefox, Opera, IE) cache images without following the HTTP expiry rules. This does not appear to be permitted by the HTML5 specification. I've got a test case for this (with explanation) here: http://ado.is-a-geek.net/expired/tests/image_cache_test.html Boris Zb

Re: [whatwg] Detached elements and delaying the load event

On 01/25/12 23:06, Ian Hickson wrote: > On Tue, 6 Sep 2011, Andrew Oakley wrote: >> >> I'm going to use the element as an example here, but the same >> thing applies to other elements such as , , . >> >> I'm going to assume that the user agent "

Re: [whatwg] HTML Audio Element removal from DOM

On Tue, Jan 17, 2012 at 1:38 PM, Eric Carlson wrote: > > On Jan 17, 2012, at 1:32 PM, Andrew Scherkus wrote: > > > On Tue, Jan 17, 2012 at 1:19 PM, Charles Pritchard > wrote: > > > >> When an element is removed from the DOM while playing, is that > >>

Re: [whatwg] HTML Audio Element removal from DOM

hem have been removed; only once a media element is in a state where no further audio could ever be played by that element may the element be garbage collected. """ Andrew

[whatwg] Detached elements and delaying the load event

f that will always work. Can we please get a clarification in HTML5, either to say that these detached objects must not be garbage collected while they are delaying the load event, or to say that they do not delay the load event. Thanks -- Andrew Oakley

Re: [whatwg] [Bug 12287] Restrict sequence to operation argument types and return types

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12287: > sequence has undesirable behaviour in JS when used as an attribute > value, so we should consider preventing its use there. HTML5 Section 10: > typedef sequence MessagePortArray; > > interface MessageEvent : Event { > readonly attribute any

[whatwg] Browser full screen and CSS media types

? Do we care to have any interaction between the full screen API and the browser full screen mode? For example, Opera switches the CSS media type to @projection and I believe is the only browser to do so. Andrew [1] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031538

[whatwg] Geolocation - Browser usability issues with regards to asking user permission

m sure there are other possible solutions, but the state of the implementation insofar as the user experience is concerned needs work. In addressing the privacy aspects of the user experience, we've created a usability issue which needs to be addressed as well. best, Andrew (P.S. I really don't kn

Re: [whatwg] html5 designers

#x27;s the best resource I've seen on HTML5 so far, and it's free to boot. Finally, I would also check out the new book from Remy Sharp and Bruce Lawson, "Introducing HTML5". I haven't read it yet, but given the authors it is sure to be good. Andrew On Mon, Mar 2

Re: [whatwg] HTML5 video: frame accuracy / SMPTE

nding. I'll land a fix for this later today. Andrew [1] https://bugs.webkit.org/show_bug.cgi?id=52697 On Wed, Jan 19, 2011 at 12:54 AM, Philip Jägenstedt wrote: > On Wed, 19 Jan 2011 05:01:14 +0100, Rob Coenen > wrote: > > I'm really happy to see that Chromium has land

Re: [whatwg] HTML5 video: frame accuracy / SMPTE

the idea, however :) Andrew On Wed, Jan 12, 2011 at 5:32 AM, Eric Carlson wrote: > > On Jan 12, 2011, at 12:42 AM, Philip Jägenstedt wrote: > > > On Wed, 12 Jan 2011 09:16:59 +0100, Glenn Maynard > wrote: > > > >> On Wed, Jan 12, 2011 at 2:49 AM, Philip Jägensted

[whatwg] PageTransitionEvent persisted data type

Is there any reason that the PageTransitionEvent persisted attribute (and corresponding argument to initPageTransitionEvent) is of type any rather than boolean? Thanks -- Andrew Oakley

Re: [whatwg] Video with MIME type application/octet-stream

owser process so implementing sniffing for a top level browser window would involve sending the bytes to a sandboxed process for inspection first. This does have a side effect where a may play fine on a page with a bogus MIME type (due to sniffing), but viewing the video URL in the browser itself would prompt a download. Andrew

Re: [whatwg] Please consider adding a couple more datetime types - type="year" and type="month-day"

>> * it has the *semantic* of being a year, which is a special type of >> number (potentially more than four digits if you subscribe to "Long >> Now"[1] methodology, or fewer than four as Andy noted). > > Why is it useful to declare this semantic to the browser? What functional

Re: [whatwg] Please consider adding a couple more datetime types - type="year" and type="month-day"

* it has the *semantic* of being a year, which is a special type of number (potentially more than four digits if you subscribe to "Long Now"[1] methodology, or fewer than four as Andy noted). >>> >>> Why is it useful to declare this semantic to the browser? What functional >>> diffe

[whatwg] Clarification on canceling events

e language that D3E uses (e.g. say that the default actions should not occur, but propagation continues)? -- Andrew Oakley

Re: [whatwg] Please consider making more generic/flexible (or renaming)

al-world conversation I had with Jeremy Keith a short while ago, is there a reason why (or the theoretical renamed less generic alternative) isn't being used inside s too, instead of another new element ()? At the time Jeremy wasn't able to give me an answer, but if it's already been discussed and I just missed it, my apologies. - Andrew

[whatwg] DOM Range Deletions

t the end point before the (as I would have expected). Thanks -- Andrew Oakley

Re: [whatwg] Offscreen canvas (or canvas for web workers).

some sort of API for blitting directly from an offscreen canvas to an onscreen one. Perhaps via a canvas ID. Andrew On Wed, Feb 24, 2010 at 6:12 AM, Maciej Stachowiak wrote: > > On Feb 24, 2010, at 1:35 AM, Jonas Sicking wrote: > > On Wed, Feb 24, 2010 at 12:14 AM, Maciej Stachowi

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

On Fri, Jan 22, 2010 at 6:58 AM, Ivan Žužak wrote: > I think there are two separate issues here. First, if this idea is to > be widely adopted and implemented - I believe there must be an open > specification of it. And there are basically two ways of doing this - > by having it proposed by a spe

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

On 22/01/2010, at 07:08, Ivan Žužak wrote: On Fri, Jan 22, 2010 at 03:33, Andrew de Andrade wrote: comments inline - A naive P2P implementation won't provide good throughput or latency because you might end up downloading files from a mobile phone on the other side of the world r

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

comments inline On Thu, Jan 21, 2010 at 8:24 PM, Mike Hearn wrote: > WebSockets doesn't let you open arbitrary ports and listen on them, > so, I don't think it can be used for what you want. that's my understanding. My question to this is if it is possible to open arbitrary ports and listen in o

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

comments inline On Thu, Jan 21, 2010 at 5:44 PM, Ivan Žužak wrote: > Hi Andrew, > > That's an interesting idea. Here are some of my thoughts: > > As your Google friend noted, I'm wondering why you'd want to implement > this on the HTML5 level, not on the browser

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

On Tue, Jan 19, 2010 at 5:31 PM, Melvin Carvalho wrote: > > > On Tue, Jan 19, 2010 at 5:59 PM, Andrew de Andrade > wrote: >> >> I have an idea for a possible use case that as far as I can tell from >> previous discussions on this list has not been considered or

Re: [whatwg] Web-sockets + Web-workers to produce a P2P website or application

lane that he worked on from 2001 to 2004. Here's the link to Brad's paper on Paper Airplane from 2005. http://codinginparadise.org/paperairplane/ -- Andrew J L de Andrade @andrewdeandrade On Tue, Jan 19, 2010 at 3:07 PM, wrote: > as someone who just listens in and is not te

[whatwg] Web-sockets + Web-workers to produce a P2P website or application

ality. This feature would basically permit a form of net neutrality by moving content to the fringes of the network. Let me know your thoughts and if you think this would be possible using Web-sockets and web-workers, and if not, what changes would be necessary to allow this to evolve. Sincerely,

Re: [whatwg] What is the purpose of timeupdate?

On Thu, Nov 5, 2009 at 6:10 AM, Brian Campbell < brian.p.campb...@dartmouth.edu> wrote: > On Nov 5, 2009, at 1:17 AM, Andrew Scherkus wrote: > > On Fri, Oct 30, 2009 at 10:18 PM, Brian Campbell < >> brian.p.campb...@dartmouth.edu> wrote: >> As a multimedia de

Re: [whatwg] Restarting the media element resource fetch algorithm after "load" event

/oncanplaythrough as alternatives to user agent checking and onload. I'm in favour of getting rid of both load and progress events. Andrew On Fri, Oct 9, 2009 at 2:27 AM, Robert O'Callahan wrote: > On Fri, Oct 9, 2009 at 8:32 PM, Philip Jägenstedt wrote: > >> Aesthetics is

Re: [whatwg] behavior

OR not_image >> - xml_mime_type AND html AND not_image >> this would be application/xhtml+xml, application/ce-html+xml etc. but >> *not* text/html >> - (xml_mime_type OR html) AND not_image >> makes sense but would certainly need clarification in the spec > > The former. I've added an "or" and removed the (redundant) HTML line to > make this clearer. Thanks. -- Andrew Oakley

[whatwg] [Replaceable] members of window

It looks like the frames and length members of the Window interface need to be [Replaceable] for web content to work correctly. I'd assume that any new attributes will probably also need the same treatment as they might otherwise clash with global variables. -- Andrew Oakley

Re: [whatwg] behavior

_mime_type OR html) AND not_image makes sense but would certainly need clarification in the spec Thanks for clarifying the other bits of the spec. -- Andrew Oakley

[whatwg] behavior

The rules in the HTML5 spec for which plugin to load for an do not seem to be followed by any browser, and in some cases are different to behavior that is common to Opera, Webkit and Gecko (I haven't tested with IE due to its lack of nsplugin support). Most notably HTML5 says that the Content-Typ

Re: [whatwg] Serving up Theora in the real world

Philip Jägenstedt wrote: > > > > Not that I except this discussion to go anywhere, but out of curiosity I > > checked how Firefox/Safari/Chrome actually implement canPlayType: > > > > http://wiki.whatwg.org/wiki/Video_type_parameters#Browser_Support > > > > Fi

[whatwg] Type of PropertyNodeList.contents

to be defined anywhere, however DOM 3 Core has a DOMStringList which seems to have this purpose. HTMLPropertyCollection.names returns a DOMStringList, so I think we should be consistent and also return a DOMStringList for PropertyNodeList.contents. -- Andrew Oakley

Re: [whatwg] Fragments included in Application Cache master entries

; manifest<http://www.whatwg.org/specs/web-apps/current-work/#attr-html-manifest>attribute. Andrew On Mon, Jul 6, 2009 at 7:13 PM, Maria Khomenko wrote: > Actually, I believe the spec does address the question in the following > passage (this is in the manifest parsing algorithm): > &

[whatwg] Fragments included in Application Cache master entries

ected here. Since fragments are not sent to servers, I can't see why they would be included in the master entry URLs as they make no difference in the content that is served. Anyone know if the spec does in fact address this issue? Andrew

Re: [whatwg] do not encourage use of small element for legal text

either normative or non-normative, about legal matters. The HTML 5 spec is going to be a terrific advance, and removing this thorn from its side will only improve it. Andrew Hagen contact2...@awhlink.com

Re: [whatwg] the cite element

x27;s intent. Smith, John. The Triumph of HTML 5. 2015. New York: Faraway Press. Regards, Andrew Hagen contact2...@awhlink.com

Re: [whatwg] the cite element

e for untitled works. For example: Rock critics have universally praisedthe untitled fourth album by Led Zeppelin. While people aren't usually typographically marked up, they are cited. The change would allow things other than titles to be placed into the cite element. That would make cite

Re: [whatwg] do not encourage use of small element for legal text

ll the points that I have made here on this topic. Andrew Hagen contact2...@awhlink.com

[whatwg] do not encourage use of small element for legal text (was: Pre-Last Call Comments)

27;s just that the HTML 5 spec will do the right thing, and not go out of its way to make legal text small and hard to read. Andrew Hagen contact2...@awhlink.com

[whatwg] the cite element

mbrace the cite element. This solution is workable. The cite element's default style is italics in display mode, and this proposal would not change that. If a web author writes: Aristotle, the web author can live with it or re-style the cite element as desired. To conclude, slightl

Re: [whatwg] Pre-Last Call Comments

@example.com";>John Smith. E-mail checked regularly. Thank you. Andrew Hagen contact2...@awhlink.com

Re: [whatwg] Can possibly work?

Ozob the Great wrote: Sorry, mail client trouble. Here is the complete message. On Sun, Sep 21, 2008 at 6:29 AM, Henri Sivonen <[EMAIL PROTECTED] > wrote: The use cases for probably aren't strong enough to warrant its addition to HTML at this stage if it had

[whatwg] [editorial] Tokeniser "tag name" state order

http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenisation.html#tag-name0 The "tag name" state has the "EOF" entry in a weird place -- in other states, "EOF" comes before "Anything else", but in this one it comes between "U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL

Re: [whatwg] Some questions

ally isn't hard thesedays -- e.g. you can download VLC and set a job going within minutes. or it's too costly to create server farms for multiple formats, etc. History shows us that even when they can, they don't. This, however, is a fair point. Andrew Sidwell

Re: [whatwg] Reasons for moving Ogg to MUST status (was Re: HTML 5, OGG, competition, civil rights, and persons with disabilities)

oubt it. IE at least would have to support it before a majority of authors would use it seriously. Andrew Sidwell

[whatwg] Removal of Ogg - eyes on you

he vendors implement it thusly. Don't buy into the FUD - it's a sign of malicious laziness and/or outright subversion, on the part of your corporate interests. -Andrew Harris http://andrewharris.org/

Re: [whatwg] Structured option element

... Having this you will be able to define many things: http://www.terrainformatica.com/htmlayout/images/selects3.jpg http://www.terrainformatica.com/htmlayout/images/selects2.jpg http://www.terrainformatica.com/htmlayout/images/grid1.jpg Andrew Fedoniouk. http://terrainfromatica.com

Re: [whatwg] Why SQL? was: Comments on updated SQL API

l also look cool there and so on. For Christmas tree such decoration approach would work but for serious system design ... Client storage shall be as simple and universal as possible to be short. Andrew Fedoniouk. http://terrainformatica.com

Re: [whatwg] Why SQL? was: Comments on updated SQL API

Ian Hickson wrote: On Mon, 24 Sep 2007, Andrew Fedoniouk wrote: I have a question: why SQL was chosen as client side storage for Web Applications? Because it's what most app developers are already used to -- the M in the widely used traditional LAMP stack is SQL. &quo

[whatwg] Why SQL? was: Comments on updated SQL API

o not understand something... Andrew Fedoniouk. http://terrainformatica.com

Re: [whatwg] Progress Events "done" event

e.gif); } Reason of my comment: I think that events like this should be reflected in CSS state flags too. CSS is a natural place to deal with this. Andrew Fedoniouk. http://terrainformatica.com [1] http://www.terrainformatica.com/sciter/Element.whtm

Re: [whatwg] Offline Web Apps

- Original Message - From: "Ian Hickson" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, August 24, 2007 11:39 AM Subject: Re: Offline Web Apps On Fri, 24 Aug 2007, Andrew Fedoniouk wr

Re: [whatwg] Offline Web Apps

" makes any or significant sense. Or even feasible as they use data flow (RPC, aka AJAX) that implies active server. I propose to clarify first what we are trying to solve. Andrew Fedoniouk. http://terrainformatica.com

Re: [whatwg] Looking at menus in HTML5...

- Original Message - From: "Křištof Želechovski" <[EMAIL PROTECTED]> To: "'Andrew Fedoniouk'" <[EMAIL PROTECTED]>; "'Ian Hickson'" <[EMAIL PROTECTED]> Cc: "'WHAT WG List'" <[EMAIL PROTECTED

Re: [whatwg] Looking at menus in HTML5...

- Original Message - From: "Křištof Želechovski" <[EMAIL PROTECTED]> To: "'Andrew Fedoniouk'" <[EMAIL PROTECTED]>; "'Ian Hickson'" <[EMAIL PROTECTED]> Cc: "'WHAT WG List'" <[EMAIL PROTECTED

Re: [whatwg] Looking at menus in HTML5...

- Original Message - From: "Křištof Želechovski" <[EMAIL PROTECTED]> To: "'Andrew Fedoniouk'" <[EMAIL PROTECTED]>; "'Ian Hickson'" <[EMAIL PROTECTED]> Cc: "'WHAT WG List'" <[EMAIL PROTECTED]

Re: [whatwg] Looking at menus in HTML5...

- Original Message - From: "Ian Hickson" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: "WHAT WG List" <[EMAIL PROTECTED]> Sent: Tuesday, August 07, 2007 7:36 PM Subject: Re: [whatwg] Looking at menus in HTML5.

Re: [whatwg] Looking at menus in HTML5...

- Original Message - From: "Ian Hickson" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: "WHAT WG List" <[EMAIL PROTECTED]> Sent: Tuesday, August 07, 2007 1:52 PM Subject: Re: [whatwg] Looking at menus in HTML5... On

  1   2   >