Re: [whatwg] Adding resourceless media to document causes error event

Chris Pearce ha scritto: I need to clarify something about the media load() algorithm [ http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#dom-media-load ] My reading of the spec is that if you have a media element with no src attribute or source element children (e.g. ) a

Re: [whatwg] RDFa is to structured data, like canvas is to bitmap and SVG is to vector

Shelley Powers ha scritto: The point I'm making is that you set a precedent, and a good one I think: giving precedence to "not invented here". In other words, to not re-invent new ways of doing something, but to look for established processes, models, et al already in place, implemented, vet

Re: [whatwg] embedding meta data for copy/paste usages - possible use case for RDF-in-HTML?

Hallvord R M Steen ha scritto: HTML5 already contains elements that can be used to help obtain this information, such as the , and it's associated heading to and . Obtaining author names might be a little more difficult, though perhaps hCard might help. Indeed. And it's not an eithe

Re: [whatwg] RDFa is to structured data, like canvas is to bitmap and SVG is to vector

Shelley Powers ha scritto: The point I'm making is that you set a precedent, and a good one I think: giving precedence to "not invented here". In other words, to not re-invent new ways of doing something, but to look for established processes, models, et al already in place, implemented, vet

Re: [whatwg] What RDF does Re: Trying to work out...

Charles McCathieNevile ha scritto: On Fri, 09 Jan 2009 12:54:08 +1100, Calogero Alex Baldacchino wrote: I admit I'm not very expert in RDF use, thus I have a few questions. Specifically, maybe I can guess the advantages when using the same (carefully modelled, and well-known) vocabular

Re: [whatwg] Trying to work out the problems solved by RDFa

Toby A Inkster ha scritto: Another reason the Microformat experience suggests new attributes are needed for semantics is the overloading of an attribute (class) previously mainly used for private convention so that it is now used for public consumption. Maybe this is true, but, personally,

Re: [whatwg] Trying to work out the problems solved by RDFa

Benjamin Hawkes-Lewis ha scritto: On 12/1/09 20:26, Calogero Alex Baldacchino wrote: I just mean that, as far as I know, there is no official standard requiring UAs to support (parse and expose through the DOM) attributes and elements which are not part of the HTML language but are found in

Re: [whatwg] Adding and removing media source elements

Philip Jägenstedt ha scritto: On Tue, 03 Feb 2009 05:44:07 +0100, Ian Hickson wrote: On Tue, 3 Feb 2009, Chris Pearce wrote: (2) Why don't we invoke load() whenever a media element's src attribute or children are changed, regardless of networkState? That way changes to the media's src/sourc

Re: [whatwg] rename CanvasPixelArray

Anne van Kesteren ha scritto: Wouldn't it make more sense to give this a more generic name, just like the object it is associated with? That way we can later reuse it for elements and the like (if we want) without it having to look silly and poorly thought out like the rest of the platform. :-

Re: [whatwg] Spellchecking mark III

Kornel Lesiński ha scritto: Probably. However, establishing that the "lang" attribute is the "first-choice" language to check (which wouldn't prevent the UA from providing other choices, or just ignoring such behaviour due to a user preference, or using other dictionaries too -- and that might

Re: [whatwg] Spellchecking mark III

Peter Kasting ha scritto: On Wed, Jan 21, 2009 at 7:38 PM, Calogero Alex Baldacchino mailto:alex.baldacch...@email.it>> wrote: Why not to let the user choose the language, as it happens in word processors? A UA can't choose accurately whether, for instance, "col

Re: [whatwg] Spellchecking mark III

Aryeh Gregor ha scritto: On Wed, Jan 21, 2009 at 4:15 AM, Mikko Rantalainen wrote: If the browser does not know the language of the content, how on earth is it supposed to *correctly* spellcheck it? I'm daily hitting a situation where browser is trying to spellcheck content with incorrect la

Re: [whatwg] Canvas arcTo all points on a line

Philip Taylor ha scritto: But I don't know if it makes sense from the perspective of someone who's got to write an independent implementation of it. Does the above explanation make more sense than the text in the spec? and if so, does it seem implementable? If so, it seems best to keep the spec'

Re: [whatwg] Issues concerning the element and xml:base

Ian Hickson ha scritto: On Fri, 16 Jan 2009, Calogero Alex Baldacchino wrote: What should happen to a linked style sheet disabled during the first casced and enabled after the has been changed? Or if it was first enabled, than disabled before changing the , and re-enabled after? For

Re: [whatwg] Issues concerning the element and xml:base

Ian Hickson ha scritto: On Thu, 15 Jan 2009, Jonas Sicking wrote: I haven't yet covered style="" attributes. The problem with CSS is that there is no clear point at which URLs are resolved... can we say it happens during parsing, so that the absolute URLs computed for the first cascade are

Re: [whatwg] Trying to work out the problems solved by RDFa

Benjamin Hawkes-Lewis ha scritto: After all, support for unknown attributes/elements has never been a standard "de jure", but more of a quirk Depends what you mean by "support" I guess. I just mean that, as far as I know, there is no official standard requiring UAs to support (parse and e

Re: [whatwg] Fuzzbot (Firefox RDFa semantics processor)

Toby A Inkster ha scritto: Calogero Alex Baldacchino wrote: The concern is about every kind of metadata with respect to their possible uses; but, while it's been stated that Microforamts (for instance) don't require any purticular support by UAs (thus they're backward compatib

Re: [whatwg] Trying to work out the problems solved by RDFa

Benjamin Hawkes-Lewis ha scritto: On 11/1/09 02:51, Calogero Alex Baldacchino wrote: eRDF might be a working compromise, because it doesn't need any changes to the spec It's not possible to author conforming HTML5 that functions as eRDF since eRDF requires a 'profile'

Re: [whatwg] Trying to work out the problems solved by RDFa

Kornel Lesiński ha scritto: On 09.01.2009, at 01:54, Calogero Alex Baldacchino wrote: This is why I was thinking about somewhat "data-rdfa-about", "data-rdfa-property", "data-rdfa-content" and so on, so that, for the purposes of an RDFa processor working on t

Re: [whatwg] Fuzzbot (Firefox RDFa semantics processor)

Manu Sporny ha scritto: Calogero Alex Baldacchino wrote: That is, choosing a proper level of integration for RDF(a) support into a web browser might divide success from failure. I don't know what's the best possible level, but I guess the deepest may be the worst, thus starti

Re: [whatwg] Trying to work out the problems solved by RDFa

Toby A Inkster ha scritto: It should be noted in this case that RDFa also allows natural language parsers to be made more useful. By looking at the RDFa which marks up the author's name and website, they may be able to determine that the comment has been written by someone other than the page

Re: [whatwg] Trying to work out the problems solved by RDFa

Ben Adida ha scritto: Ian Hickson wrote: We have to make sure that whatever we specify in HTML5 actually is going to be useful for the purpose it is intended for. If a feature intended for wide-scale automated data extraction is especially susceptible to spamming attacks, then it is unlikel

Re: [whatwg] Trying to work out the problems solved by RDFa

Ben Adida ha scritto: Tab Atkins Jr. wrote: Actually, SearchMonkey is an excellent use case, and provides a problem statement. I'm surprised, but very happily so, that you agree. My confusion stems from the fact that Ian clearly mentioned SearchMonkey in his email a few days ago, then

Re: [whatwg] Trying to work out the problems solved by RDFa

Julian Reschke ha scritto: Calogero Alex Baldacchino wrote: ... This is why I was thinking about somewhat "data-rdfa-about", "data-rdfa-property", "data-rdfa-content" and so on, so that, for the purposes of an RDFa processor working on top of HTML5 UAs (perhaps

Re: [whatwg] Trying to work out the problems solved by RDFa

Charles McCathieNevile ha scritto: On Mon, 05 Jan 2009 01:21:33 +1100, Henri Sivonen wrote: On Jan 2, 2009, at 14:01, Benjamin Hawkes-Lewis wrote: On 2/1/09 10:38, Henri Sivonen wrote: Is the problem in the case of recipes that the provider of the page navigation around the recipe is unwill

Re: [whatwg] Trying to work out the problems solved by RDFa

Charles McCathieNevile ha scritto: On Sun, 04 Jan 2009 03:51:53 +1100, Calogero Alex Baldacchino wrote: Charles McCathieNevile ha scritto: ... it shouldn't be too difficoult to create a custom parser, comforming to RDFa spec and availing of data-* attributes... That is, since RDFa c

Re: [whatwg] Trying to work out the problems solved by RDFa

Toby A Inkster ha scritto: Calogero Alex Baldacchino wrote: My concern is: is RDFa really suitable for everyone and for Web automation? My own answer, at first glance, is no. That's because RDF(a) can perhaps address nicely very niche needs, where determining how much data can be trust

Re: [whatwg] Trying to work out the problems solved by RDFa

Dan Brickley ha scritto: On 3/1/09 14:02, Julian Reschke wrote: Tab Atkins Jr. wrote: The most successful alternative is nothing at all. ^_^ We can extract copious data from web pages reliably without metadata, either using our human senses (in personal use) or natural-language-based processing

Re: [whatwg] Trying to work out the problems solved by RDFa

Charles McCathieNevile ha scritto: The results of the first set of Microformats efforts were some pretty cool applications, like the following one demonstrating how a web browser could forward event information from your PC web browser to your phone via Bluetooth: http://www.youtube.com/watch?

Re: [whatwg] Spellchecking mark III

Maciej Stachowiak ha scritto: On Dec 31, 2008, at 12:26 PM, Robert O'Callahan wrote: On Thu, Jan 1, 2009 at 4:15 AM, Maciej Stachowiak > wrote: 2) The proposal Hixie linked seems way overengineered for this purpose. First, it allows spellchecking to be explicitl

Re: [whatwg] Spellchecking mark III

Calogero Alex Baldacchino ha scritto: The language to check might be choosen from several sources, such as the 'lang' attribute of the contenteditable element itself, if different from the document language. For instance, a blog editor's interface document might not be

Re: [whatwg] Spellchecking mark III

Robert O'Callahan ha scritto: 2008/12/31 Giovanni Campagna > 2008/12/30 timeless mailto:timel...@gmail.com>> On Tue, Dec 30, 2008 at 5:20 PM, Kornel Lesiński mailto:kor...@geekhood.net>> wrote: > It's useful for fields that contain n

Re: [whatwg] Thoughts on video accessibility

Silvia Pfeiffer ha scritto: Hi Ian, Thanks for taking the time to go through all the options, analyse and understand them - especially on your birthday! :-) Much appreciated! Than, happy birthday to Ian! [...] The only real issue that we have with separate files is that the captions may g

Re: [whatwg] with omitted tags

Geoffrey Sneddon ha scritto: On 26 Dec 2008, at 17:02, Calogero Alex Baldacchino wrote: Philip Taylor ha scritto: I can start with a simple document that's probably conforming and that the validator doesn't complain about: Then I can read the "Writing HTML document

Re: [whatwg] with omitted tags

Philip Taylor ha scritto: I can start with a simple document that's probably conforming and that the validator doesn't complain about: Then I can read the "Writing HTML document: Optional tags" section, which says: "A head element's end tag may be omitted if the head element is not immedi

Re: [whatwg] Merry Christmas!

Giovanni Campagna ha scritto: Probably you didn't notice, but it is 25th December today. Merry Christmas and Happy New Year to all members of WHAT and W3C working groups! Giovanni Merry Christmas to you and to everyone celebrating Christmas! Happy and holy celebrations to everyone celebrat

Re: [whatwg] Phrasing semantics feedback omnibus

Ian Hickson ha scritto: On Sun, 30 Nov 2008, Calogero Alex Baldacchino wrote: [...] an element [...] I encourage you to look at the element in HTML5. I'm waiting for implementations of that before looking at access keys. I've given a closer look to it and (more quick

Re: [whatwg] Phrasing semantics feedback omnibus

't consume HTML _code_? And how should a machine be supposed to consume HTML code if it's not projected having in mind machine constraints _first_ (e.g. context-freedom), authors needs in second place? :-) On Tue, 25 Nov 2008, Calogero Alex Baldacchino wrote: [...] Could you give a co

[whatwg] A few hints on html5 - part 4

Miscellaneous The Window interface open method accepts a "features" argument for historical (and backward compatibility) reasons, which, as stated, has no actual effect. I was considering the opportunity, instead, of maintaining the old functionality as an alternative and redundant implement

[whatwg] A few hints on html5 - part 3

About the cross-document messaging Let's consider the following scenario. A somewhat productivity suite (or any sort of "web applications collection") is made up of a few different top-level/auxiliary browsing contexts - let's call each one a "module" - eventually from different origins, and e

[whatwg] A few hints on html5 -- part 2

About the RemoteEventTarget interface The removeEventSource() method is provided to remove one instance of a source (one matching URL) per invocation, but no way is defined to know whether other instances are yet listed, or if the operation succeeded. Maybe such method could return a boolean v

[whatwg] A few hints on html5 - part 1

Let me suggest a few hints on html5 specs, maybe some hints will be minor or less important, maybe some others might be useful for a somewhat next version of these specifications. Let me also apologize if the following points have been yet discussed and I'm missing such discussions, or if I've

Re: [whatwg] URL parsing and same-document references [was: Re: Citing multiple elements in HTML5]

Nils Dagsson Moskopp ha scritto: Am Samstag, den 13.12.2008, 19:09 +0100 schrieb Calogero Alex Baldacchino: Actually I'm not from any faction, to be honest. I think a rationale for that may be "people write strange things, both in address bars and in html code", thus rela

Re: [whatwg] URL parsing and same-document references [was: Re: Citing multiple elements in HTML5]

Nils Dagsson Moskopp ha scritto: Am Freitag, den 12.12.2008, 20:36 +0100 schrieb Calogero Alex Baldacchino: The above (but the 'double check' I was suggesting) is about the way Firefox (2.x and 3.0.4) behaves (both href="#foo%20bar" and, in a different page, href="

Re: [whatwg] When closing the browser

Ian Hickson ha scritto: On Fri, 12 Dec 2008, Bil Corry wrote: Speaking of 'onbeforeunload' and 'beforeunload' -- it'd be helpful if there was a way to distinguish between the user taking an action which leaves the site vs. taking an action that returns to the site. For privacy, it shouldn'

Re: [whatwg] salvaging work while navigating away from a web app -- onunload="confirm('save before quitting?')

Bil Corry ha scritto: Ojan Vafai wrote on 12/12/2008 12:49 PM: If we're going for matching what browsers do, there's a number of cases (different in each browser) where the confirm doesn't popup. In Chrome, for example, if the beforeunload handler takes too long, we kill it and navigate away.

Re: [whatwg] URL parsing and same-document references [was: Re: Citing multiple elements in HTML5]

Calogero Alex Baldacchino ha scritto: Maybe the above needs a further clarification. Let me start from URL parsing (and resolving) rules: after the URL is validated, it's divided into its components, but nothing is stated about normalization and/or %-encoded characters. I think that apply

Re: [whatwg] When closing the browser

Bil Corry ha scritto: Speaking of 'onbeforeunload' and 'beforeunload' -- it'd be helpful if there was a way to distinguish between the user taking an action which leaves the site vs. taking an action that returns to the site. E.g.: leaves site: closes browser

Re: [whatwg] Use cases for Node.getElementById

Garrett Smith ha scritto: On Wed, Dec 10, 2008 at 8:10 AM, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: Garrett Smith ha scritto: On Sat, Dec 6, 2008 at 7:09 PM, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: Simon Pieters ha scritto: On

Re: [whatwg] Use cases for Node.getElementById

Garrett Smith ha scritto: On Sat, Dec 6, 2008 at 7:09 PM, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: Simon Pieters ha scritto: On Fri, 05 Dec 2008 19:19:04 +0100, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: [...] (I'm currently t

Re: [whatwg] Thoughts on video accessibility

Silvia Pfeiffer ha scritto: On Wed, Dec 10, 2008 at 6:59 AM, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: Anyway, the use of subtitles in conjunction with screen readers might be problematic: a deeper synchronization with the media might be needed in order to have the text rea

Re: [whatwg] Thoughts on video accessibility

Silvia Pfeiffer ha scritto: I heard some complaints about there not being any implementation of the suggestions I made. So here goes: 1. out-of-band There is an example of using srt with ogg in a out-of-band approach here: http://v2v.cc/~j/jquery.srt/ You will need Firefox3.1 to play it. The sy

Re: [whatwg] Use cases for Node.getElementById

ddailey ha scritto: There are lots of times in which I've needed to examine one document by use of a script that resides inside another. Using lists of attributes to do that has been rather important, though if those lists were accessible as properties of objects rather than as nodes themselve

Re: [whatwg] Use cases for Node.getElementById

Jonas Sicking ha scritto: I see the Element interface no more contains methods to handle Attr nodes: since those are described as not being child nodes of an Element, in W3C specifications, there will be any other way to handle attributes as nodes, the 'nature' of Attr nodes is going to change

Re: [whatwg] Use cases for Node.getElementById

Simon Pieters ha scritto: On Sun, 07 Dec 2008 04:09:01 +0100, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: I'm reading it :-) And I have a few questions. First, is it meant as the reference DOM Core for HTML 5 only, or in general (for other kinds of markup too)? In ge

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: What terminology would you prefer rather than "subtree"? (We can't say document, since we are also trying to define conformance rules for disconnected subtrees handled from scripts.) I was thinking again on that. Let me suggest something like the following (and just

Re: [whatwg] Use cases for Node.getElementById

João Eiras ha scritto: IMO, anyone suggesting a Node.getElementById clearly does not know very well how getElementById is supposed to work. There are ways to transverse a DOM tree currently, either DOM properties and methods, XPath, selectors API and such. Considering ids are required to be un

Re: [whatwg] Use cases for Node.getElementById

Simon Pieters ha scritto: On Fri, 05 Dec 2008 19:19:04 +0100, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: [...] (I'm currently the editor of that proposal, currently located at http://simon.html5.org/specs/web-dom-core ) I'm reading it :-) And I have a few

Re: [whatwg] Early feedback on header association algorithm

Aaron Leventhal ha scritto: How about node.getElementByIdInSubtree? On 12/2/2008 4:07 PM, timeless wrote: On Tue, Dec 2, 2008 at 10:39 AM, Aaron Leventhal<[EMAIL PROTECTED]> wrote: Maybe there is a deeper problem if copy& paste doesn't work right because of IDs? Or maybe there should be

[whatwg] URL parsing and same-document references [was: Re: Citing multiple elements in HTML5]

Calogero Alex Baldacchino ha scritto: Maybe the first is wrong, and I'm still unsure of the second. My concern is, a character-by-character comparison between an id value and a fragment identifier may fail several ways. What for href="#foo bar " and id="foo bar "?

Re: [whatwg] Handling in the "after head" insertion mode

Tommy Thorsen ha scritto: For the record, the following markup: results in: with the current algorithm, because the "in body" insertion mode treats as if it was a . Maybe not fully in topic. Section 4.5.3 says, "|br| elements must be empty. Any content inside |br| ele

Re: [whatwg] Citing multiple elements in HTML5

Jonas Sicking ha scritto: > > In firefox we now always return the first element with the requested > ID. I think IE does the same. This seems equally reliably and much > less likely to cause page breakage or interoperability issues. > > That's reasonable, and I pointed out that should be stan

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: It's intended as a replacement for DOM3 Core, I believe. Then, I hope in a convergence with the W3C, as it's one of the goal of the WHATWG. I believe neither organizations wish a heavy standard fragmentation. -- Caselle da 1GB, trasmetti allegati fino a 3GB e in

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: On Wed, 3 Dec 2008, Calogero Alex Baldacchino wrote: But, isn't it worth to spend a word everywhere in the spec to tell when it's a quirck for backward compatibility, which might go away in the future, and when it's not, because that's not needed

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: Exactly how getElementById() works is out of scope for HTML5, but in the Web DOM Core spec that Simon is working on I imagine he has specced that it will pick the first element with a matching ID or some such behavior. Cheers, Is it thought as a somewhat break with w

Re: [whatwg] Citing multiple elements in HTML5

Benjamin Hawkes-Lewis ha scritto: Calogero Alex Baldacchino wrote: [...] I think you're confusing parsing rules that conforming user agents must follow to associate identifiers with elements (even when ids are duplicated) with the authoring rules that conforming documents must follow

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: On Mon, 1 Dec 2008, Calogero Alex Baldacchino wrote: Yes, a hash link () will scroll to the element with an id=foo. If coding properly, you'll virtually *never* use an for an actual *anchor*, but rather will target the most semantically appropriate element,

Re: [whatwg] Citing multiple elements in HTML5

Tab Atkins Jr. ha scritto: [[off list]] Well, in fact, the above could be done as well by 'playing' with anchors (but is it still possible to set an anchor somewhere in the document, such as ? I haven't found examples for that, perhaps I'm missing something...). Yes, a hash link () wi

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: On Sun, 30 Nov 2008, Calogero Alex Baldacchino wrote: I'm not sure I'm understanding the whole function of the element, and perhaps I'm bothering again with ids and references, but the relationship between a and a quotation could be disambiguated by

Re: [whatwg] Fallback styles for legacy user agents [was: Re: Deprecating , ?]

timeless ha scritto: i don't really want to spend a lot of time with this, but any feature authors are provided will be abused. among my list of things which i wish were never let out of pandora's box are defining accesskeys (instead of commands) in html, and another which i'd hope dies on the v

Re: [whatwg] Citing multiple elements in HTML5

Henri Sivonen ha scritto: On Nov 30, 2008, at 18:38, Calogero Alex Baldacchino wrote: I'm not sure I'm understanding the whole function of the element, [...] Q: What problem does it solve? The element solves the problem that if one considers evil (I don't) and one want

Re: [whatwg] Citing multiple elements in HTML5

Ian Hickson ha scritto: I've removed the offending text. I don't think we can say that quotes should always come before their citations. For example, it's easy to imagine a blog that says: Book The First says: ...from book 1... But Book The Second says: ...from book 2... ...which

Re: [whatwg] Deprecating , ?

Tab Atkins Jr. ha scritto: On Wed, Nov 26, 2008 at 4:48 PM, Calogero Alex Baldacchino <[EMAIL PROTECTED]> wrote: [cut] We don't have to touch parsing at all to accomplish essentially this.The issue you're worried about is getting crazy semantics applied to in

Re: [whatwg] accesskey attribute with display:none elements

Olli Pettay ha scritto: On 11/27/2008 06:52 PM, Calogero Alex Baldacchino wrote: Perhaps a *good* rationale could be, "if you can't see the control, There are other modalities than just visual. Indeed, and the display property applies to every and each the very same way. From htt

Re: [whatwg] Fallback styles for legacy user agents [was: Re: Deprecating , ?]

Benjamin Hawkes-Lewis ha scritto: Calogero Alex Baldacchino wrote: That worked fine on Opera 9 and FF2, but, when tried on IE7, the show became a little weird... the element was there, the style attribute was regarded as for any other element (display:block worked), but didn't applied t

Re: [whatwg] Feeedback on , , and other elements

Pentasis ha scritto: From: Ian Hickson <[EMAIL PROTECTED]> Subject: Re: [whatwg] Feeedback on , , and other elements related to cross-references To: Calogero Alex Baldacchino <[EMAIL PROTECTED]> Cc: WHAT Working Group Message-ID: <[EMAIL PROTECTED]> Content-Type: TEXT/PLAIN

Re: [whatwg] Fallback styles for legacy user agents [was: Re: Deprecating , ?]

Benjamin Hawkes-Lewis ha scritto: Calogero Alex Baldacchino wrote: The "foundation" style sheet may be at least a partial solution, but if the browser is not aware of an element, I guess its style could not apply at all. For popular browsers, at least, this guess is wrong. Unknow

Re: [whatwg] accesskey attribute with display:none elements

Olli Pettay ha scritto: On 11/26/2008 05:35 PM, Calogero Alex Baldacchino wrote: anyway I think key events handling may be improved and become easier to adopt by adding to a somewhat interface a few constants representing the modifiers combination used by the browser to activate access keys, so

Re: [whatwg] Feeedback on , , and other elements related to cross-references

Ian Hickson ha scritto: On Thu, 27 Nov 2008, Calogero Alex Baldacchino wrote: Perhaps a silly idea: what if abbreviations could work as an img-map couple? That is, i.e., an without a title could avail of a, let's say, 'ref' attribute indicating the id of a previous element wit

Re: [whatwg] Feeedback on , , and other elements related to cross-references

Ian Hickson ha scritto: On Wed, 23 Apr 2008, Jon Gibbins (dotjay) wrote: In my opinion, a more useful solution is to offer some form of infrastructure for glossaries where abbreviations can be uniquely identified to an expanded form. This would aid disambiguation and give control of rendering

Re: [whatwg] Deprecating , ?

Tab Atkins Jr. ha scritto: On Tue, Nov 25, 2008 at 3:08 PM, Calogero Alex Baldacchino <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Tab Atkins Jr. ha scritto: On Tue, Nov 25, 2008 at 10:24 AM, Calogero Alex Baldacchino <[EMAIL PROTECTED] <mailt

Re: [whatwg] Solving the login/logout problem in HTML

artin Atkins ha scritto: > Asbjørn Ulsberg wrote: >> >> [Request 1] >> >> GET /administration/ HTTP/1.1 >> >> >> [Response 1] >> >> HTTP/1.1 401 Unauthorized >> WWW-Authenticate: HTML realm="Administration" >> >> >> >> >> >> >> >> >> >> >> >> >> [Reque

Re: [whatwg] Fallback styles for legacy user agents [was: Re: Deprecating , ?]

Benjamin Hawkes-Lewis ha scritto: Calogero Alex Baldacchino wrote: I know, and agree with the basic reasons; however I think that deriving an SGML version (i.e. by adding new entities and elements, as needed, to an html 4 dtd) should not be very difficoult, and could be worth the effort (i.e

Re: [whatwg] accesskey attribute with display:none elements

Olli Pettay ha scritto: On 11/26/2008 02:34 AM, Calogero Alex Baldacchino wrote: A better way to do what you aim would consist of setting a listener for key events on a displayable element and choosing a different operation basing on the pressed key(s); This is not content author friendly way

Re: [whatwg] accesskey attribute with display:none elements

Olli Pettay ha scritto: On 11/25/2008 11:17 PM, Calogero Alex Baldacchino wrote: > Maybe, the standard behaviour (for both 'display:none' and > 'visibility:hidden') could be just focusing (and changing visibility) > after pressing the access key (so the user noti

Re: [whatwg] Issues relating to the syntax of dates and times

Ian Hickson ha scritto: On Tue, 25 Nov 2008, Calogero Alex Baldacchino wrote: In other words, the normative section of the spec will be as generic as possible, while a non-normative section will cover a bounch of use cases and examples, without pretending to be exahustive with regard to all

Re: [whatwg] Issues relating to the syntax of dates and times

Lachlan Hunt ha scritto: Pentasis wrote: Ian Hickson wrote: On Tue, 25 Nov 2008, Pentasis wrote: "The primary use cases for these elements are for marking up publication dates e.g. in blog entries, and for marking event dates in hCalendar markup. Thus the DOM APIs are likely to be used as way

Re: [whatwg] accesskey attribute with display:none elements

Olli Pettay ha scritto: Hi all, currently it isn't specified anywhere (AFAIK) what should happen if the element which has an accesskey attribute is hidden using display:none. HTML4 says the following: "Pressing an access key assigned to an element gives focus to the element. The action that oc

Re: [whatwg] Deprecating , ?

Tab Atkins Jr. ha scritto: On Tue, Nov 25, 2008 at 10:24 AM, Calogero Alex Baldacchino <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Of course that's possible, but, as you noticed too, only by redefining the semantics, and is not a best choice per se

Re: [whatwg] media elements: Relative seeking

Eric Carlson ha scritto: On Nov 24, 2008, at 2:21 PM, Calogero Alex Baldacchino wrote: Well, the length attribute could be an indication about such limit and could accept a generic value, such as 'unknown' (or '0', with the same meaning - just to have only numerical va

Re: [whatwg] Deprecating , ?

Smylers wrote: Asbjørn Ulsberg writes: On Mon, 17 Nov 2008 15:26:22 +0100, Smylers <[EMAIL PROTECTED]> wrote: In printed material users are typically given no out-of-band information about the semantics of the typesetting. However, smaller things are less noticeable, and it's general

Re: [whatwg] media elements: Relative seeking

  - Original Message Da: "Maik Merten" <[EMAIL PROTECTED]> To: "WHATWG Proposals" Oggetto: Re: [whatwg] media elements: Relative seeking Data: 24/11/08 08:45 > Eric Carlson schrieb: >> QuickTime has used this method this since it started

Re: [whatwg] media elements: Relative seeking

- Original Message Da: "Eric Carlson" <[EMAIL PROTECTED]> To: "Silvia Pfeiffer" <[EMAIL PROTECTED]> Cc: "WHAT Working Group" , "Maik Merten" <[EMAIL PROTECTED]> Oggetto: Re: [whatwg] media elements: Relative seeking Data: 24/11/08 03:17 > Silvia