Re: [whatwg] Changing punctuation value of input element in telephone state

On 04/07/2010 03:49 AM, Mikko Rantalainen wrote: And nowadays you will see stuff like this: +358 (012) 1234 567 This contains the area code for Finland "+358" in addition to the Finnish "local distance number". However, there's a catch! When dialing, you must press +358121234567 because the firs

Re: [whatwg] Window id - a proposal to leverage session usage in web application

Sebastian Hennebrueder wrote: thank you for the feedback. I hope that I see your point correctly. You are right, that for JavaScript based applications this can easily be solved with a sessionStorage. All technologies around GoogleWebToolkit, Dojo, Echo etc which hold the state in the client

Re: [whatwg] URN or protocol attribute

Brett Zamir wrote: Hi, Internet Explorer has an attribute on anchor elements for URNs: http://msdn.microsoft.com/en-us/library/ms534710%28VS.85%29.aspx This has not caught on in other browsers, though I believe it could be a very powerful feature once the feature was supported with a UI tha

Re: [whatwg] Making cross-domain overlays more user-friendly

Rowan Nairn wrote: Hi, In the spirit of paving some cow paths I'd like to put forward a proposal for a future version of HTML. The behavior I'm addressing is sites that replace links to external content with a framed version of that content, along with their own overlay of information and links

Re: [whatwg] Canvas - Exception on arc with negative radius

Dirk Schulze wrote: Another example is: http://blahbleh.com/molecools.php?name=1,2% 20dimethylcyclopropane If you turn the molecule a bit, the circles disappear with a INDEX_SIZE_ERR exception. Isn't it better to just ignore the arc and go on with the drawing, like Firefox does? And perhaps th

Re: [whatwg] Persistent SharedWorkers

Drew Wilson wrote: - Permissions: Installing a persistent worker is essentially giving a web application a near-permanent footprint on your PC - we need explicit permission from the user, and we need some mechanism in the user agent to revoke this permission. There are a number of examples of

Re: [whatwg] Warnings for non-applicable properties

Ian Hickson wrote: On Mon, 10 Nov 2008, Paul Arzul wrote: is it unfortunate that the html4 stylesheet is only informative? perhaps html5 could then consider giving us a normative default user agent stylesheet - or at least a normative version with only display properties. The spec has a semi

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

Ian Hickson wrote: They have already solved some problems with RDF and wish only to adapt this generalized solution to work in HTML, while you wish to re-solve all of these problems from the ground up. I don't necessarily wish to resolve the problems -- if they have existing good solutions,

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

Ian Hickson wrote: The question we should be discussing is not "should it work?" (because it already does), but rather, "should it validate?" No, the question is "what problem are we solving?". Talking about RDFa, RDF, eRDF, Microformats, and so forth doesn't answer this question. The ques

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

Toby A Inkster wrote: 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 compatible), RDFa would be a co

Re: [whatwg]

Maciej Stachowiak wrote: In the case of Safari, we store the generated private key in the Keychain, and sites using typically respond with a signed certificate, which is downloaded and automatically added to the Keychain. Depending on the valid purposes of the key, users can then do the fol

Re: [whatwg] Modal dialogs in HTML5

Philipp Serafin wrote: timeless schrieb: On Thu, Dec 25, 2008 at 8:29 PM, Philipp Serafin wrote: Well, you could still phrase it something along the lines of "The size of a popup document's viewport SHOULD be calculated using the CSS shrink wrap algorithm... etc etc". as an embedder

Re: [whatwg] Embedding images within editable content

Tab Atkins Jr. wrote: On Mon, Dec 22, 2008 at 1:33 PM, Martin Atkins wrote: However, I'm not sure what the solution is here. If contentEditable was a "real" form widget you could imagine it supporting a multipart/form-data upload of all of its contained images, or something. H

Re: [whatwg] Embedding images within editable content

Tab Atkins Jr. wrote: On Mon, Dec 22, 2008 at 2:53 AM, Shital Shah wrote: I'm wondering if there are any ideas being discussed to add an ability so users can embed images in editable areas. [snip] I'm confused about what you're asking. All decent WYSIWYG editors *do* allow users to insert

Re: [whatwg] Stability of tokenizing/dom algorithms

Edward Z. Yang wrote: Ian Hickson wrote: I'm not saying don't be standards-compliant; I'm just saying use a subset of HTML5 that you feel comfortable with (which might also be a subset of HTML4, for that matter, just with the HTML5 DOCTYPE so that you don't have to worry about exactly which ve

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

timeless wrote: On Fri, Dec 12, 2008 at 10:01 PM, Martin Atkins wrote: I think this makes a good case for not allowing any site to create browser-modal UI. Could browsers handle confirm() and friends in such a way that they only block the contents of the tab, not the whole browser? sure

Re: [whatwg] When closing the browser

Ian Hickson wrote: On Fri, 12 Dec 2008, Bil Corry wrote: Or maybe it'd be better if non-persistent cookies are removed once the user no longer has an open tab to the site, instead of using a JavaScript-based solution. This could be done now; I recommend bringing this up with browser vendors

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

Bil Corry wrote: Here's a fun one, I made this as a demo to show how a website could trap a user forever: http://www.corry.biz/neverleave.lasso I haven't tried it in any browsers lately, but a quick test with IE7 shows it still is effective (for it at least). I think this makes a

Re: [whatwg] Thoughts on video accessibility

Silvia Pfeiffer wrote: I'm interested to hear people's opinions on these ideas. I agree with Ralph and think having a simple, explicit mechanism at the html level is worthwhile - and very open and explicit to a web author. Having a redirection through a ROE-type file on the server is more opaque

Re: [whatwg] Thoughts on video accessibility

Silvia Pfeiffer wrote: Take this as an example: http://example.com/video.ogv"; controls> Could this combining of resources be achieved instead with SMIL or some other existing format? If there is already a format for doing this then I think HTML should avoid re-inventing it unle

Re: [whatwg] video tag: pixel aspect ratio

Pierre-Olivier Latour wrote: Regarding the stretch attribute, we should have this functionally available to users but preferably at the CSS level. It would also be useful if this mechanism were available for images. A bunch of times I've written code to proportionally scale images to crea

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

Ian Hickson wrote: On Wed, 26 Nov 2008, Philip Taylor wrote: If I'm not misunderstanding things, there is a new attack scenario: I post a comment on someone's blog, saying href="/restricted-access.php?xsshole=action=http://hacker.example.com/capture name=login>name=username>">crawl me! Hm,

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

Julian Reschke wrote: You can already handle the case of content that's available unauthenticated, but would potentially differ in case of being authenticated by adding Vary: Authorization to a response. According to section 14.8 of the HTTP 1.1 specification, the presence of the Auth

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

Asbjørn Ulsberg wrote: [Request 1] GET /administration/ HTTP/1.1 [Response 1] HTTP/1.1 401 Unauthorized WWW-Authenticate: HTML realm="Administration" [Request 2] POST /login HTTP/1.1 username=admin&password=secret [Response 2] HTTP/1.

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

Julian Reschke wrote: Martin Atkins wrote: This idea has promise, but is it compatible with existing browsers? The case where the only challenge included is HTML is probably okay, since browsers will at this point likely determine that they don't support any of the given schemes and

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

Ian Hickson wrote: It seems to me that the first limitation of form authentication could be removed by inventing a new WWW-Authenticate challenge that means "reply to the form in the page". I have now specified such a value in HTML5 (since it is specific to entity bodies that contain HTML for

Re: [whatwg] [rest-discuss] HTML5 and RESTful HTTP in browsers

Hallvord R M Steen wrote: I've built two-three websites that use content/language negotiation and I now consider it an architectural mistake to rely on negotiation because the URLs no longer uniquely identify the variants I in many scenarios need to identify. It's OK-ish to do it as a pure forma

Re: [whatwg] fixing the authentication problem

Eduard Pascual wrote: Not similar at all: for unencrypted connections, you have the "don't bother me again" option, in the form of an obvious checkbox; while with self-signed certificates you are "warned" continuously; with the only option to "install" the certificate on your system to trust it (

Re: [whatwg] Proposal for a link attribute to replace

Ian Hickson wrote: This proposal would circumvent 's main limitation which is its requirement to not wrap block-level elements or 'interactive' content. The HTML5 draft requires it wrap 'phrasing content' (essentially paragraphs) and not wrap 'interactive' content (such as other hyperlinks)

Re: [whatwg] The sizes="" attribute for rel=icon

Ian Hickson wrote: In general I agree that attributes are not a scarce resource, but if you need to add use-specific attributes to a supposedly-generic element I think that indicates that the generic element is inappropriate for the use-case. I disagree. Look at , for instance. I wouldn'

Re: [whatwg] The element and sandboxing ideas

Ian Hickson wrote: Summary: * I've added a sandbox="" attribute to , which by default disables a number of features and takes a space-separated list of features to re-enable: [snip list] Unless I'm missing something, this attribute is useless in practice because legacy browsers will n

Re: [whatwg] aRe:

Ian Hickson wrote: Using media queries for this is serious overkill. I can easily imagine uses for this that are from code that doesn't have a media queries implementation available, and this isn't something that implementors are going to implement media queries for. We need a solution that

Re: [whatwg]

Lachlan Hunt wrote: Martin Atkins wrote: Lachlan Hunt wrote: Martin Atkins wrote: Could this be said about size as well? No, because the media queries are related to the actual tech specs of the device, not the image. I'm fairly sure there are no 16x16px screens in use, at leas

Re: [whatwg]

Lachlan Hunt wrote: Martin Atkins wrote: Lachlan Hunt wrote: For color, you are reinventing Media Queries. For compression, you are basically reinventing q values for MIME types. Could this be said about size as well? No, because the media queries are related to the actual tech specs

Re: [whatwg]

Lachlan Hunt wrote: Charles Iliya Krempeaux wrote: ... could become... For color, you are reinventing Media Queries. For compression, you are basically reinventing q values for MIME types. Could this be said about size as well? Here I'm assuming that "the rendering surface of

Re: [whatwg]

Ian Hickson wrote: (With my rarely-used Google hat on:) The Gears team has an API that allows authors to specify a set of icons: http://code.google.com/apis/gears/upcoming/api_desktop.html They used a scripted API, but when I tried to get them to use a declarative API, they said that the m

Re: [whatwg] postMessage feedback

Jeff Walden wrote: Ian Hickson wrote: I haven't changed the target of the event, it's still the Document object. This is a little odd, though, would people rather I made it the element with an auto-forward to the Window object, like the 'load' event and so forth? That would allow onmessage=""

Re: [whatwg] Element borders as resizable handles

Greg Houston wrote: While on the topic of borders, it would also be nice if there was a CSS property for their alignment, "outside" as is the current default, and "inside". Pushing my luck, I would like to see the same options for the strokes in the canvas element with the addition of "center" w

Re: [whatwg] ALT and equivalent representation

Shannon wrote: The ONLY "business" justification I have for using alt tags is that a w3c valid site REQUIRES them and this may increase the sites Google rank (which is just speculation really). If you take the requirement out to use them on every image in a valid site then you take away much

Re: [whatwg] Some questions

Charles wrote: Maciej, But I think the premise of the question misses the point of the element. I may very well be completely missing the point. I'll be satisfied if someone tells me that is not intended to be the preferred way to embed video on web pages, in which case I'll quietly return

Re: [whatwg] HTML5 Edit Link Relation

James M Snell wrote: This is just off the top of my head so I'm certain that there are probably reasons why this wouldn't work, but could we not do something like, http://example.org/foo"; /> Edit indicates the purpose of the link, put, delete and patch indicate methods (in addition to GET).

Re: [whatwg] Web forms 2, input type suggestions

Lachlan Hunt wrote: Martin Atkins wrote: Lachlan Hunt wrote: http://www.haymespaint.com.au/haymes/colourcentre/ http://www.ficml.org/jemimap/style/color/wheel.html http://wellstyled.com/tools/colorscheme2/ These are some rather contrived examples. How can you possibly call them contrived

Re: [whatwg] Web forms 2, input type suggestions

Lachlan Hunt wrote: Here's a few sites I found that ask the user to select colours. http://www.haymespaint.com.au/haymes/colourcentre/ http://www.ficml.org/jemimap/style/color/wheel.html http://wellstyled.com/tools/colorscheme2/ I can't figure out how any of those would benefit from the new in

Re: [whatwg] Web forms 2, input type suggestions

Benjamin Joffe wrote: Have the following possible values for the TYPE attribute been considered for the INPUT element? type="color" The user agent would display an appropriate colour picker and would send a hexidecimal string represting that colour to the server. I like this idea. It's simpl

Re: [whatwg] Proposal: Allow block content inside label element

Brad Fults wrote: Currently, as far as I can tell, in HTML 4 [1] and HTML 5 [2], the label element is defined as having inline content. When using the implicit form control association pattern described in the HTML 4 spec (e.g. a form control inside of the label element instead of or in addition

Re: [whatwg] classList.toggle()

Maciej Stachowiak wrote: How about about adding a toggle() operation to classList? Adds the token if not present, removes it if present. This would be useful for script code that dynamically manipulates classes to cause style changes. It's been my experience that toggles are troublesome.

Re: [whatwg] Script, style and backwards compatibility

Simon Pieters wrote: This could thus also imply: * Don't disallow lang="" in XHTML5 * Don't disallow in XHTML5. * Don't disallow in XHTML5 (it doesn't do any good, but doesn't harm either). When using these, though, generic XML tools (i.e., those that aren't XHTML-aware) won't "see"

Re: [whatwg] element

Christian Schmidt wrote: In practice, the result effect is often achieved by wrapping your include file in a document.write() and including this using script a

Re: [whatwg] HTTP's Referer and Set-Cookie2 headers

Nicholas Shanks wrote: May I suggest that you also allow the DOM "referrer" attribute to match a HTTP "Referrer" header if one is present, and fall back to the "Referer" header otherwise. This provides for HTML 5 compliant UAs to be forwards compatible with a potential future HTTP spec that fix

Re: [whatwg] Conformance for Mail clients (and maybe other WYSIWYGeditors)

Kristof Zelechovski wrote: I think the correct fallback for a photograph for its own sake is alt="(Use a browser that supports graphic images to view)". That is basically what happens if you omit the alt attribute altogether. My graphical browsers (when I turn off images) write "Image" in plac

Re: [whatwg] WF2: Non-validating submit buttons

Anne van Kesteren wrote: On Wed, 04 Apr 2007 14:05:44 +0200, Christian Schmidt <[EMAIL PROTECTED]> wrote: It would be useful to be able to mark certain submit buttons as non-validating. There appears to be at least some demand for such a feature, and so far there has been no negative respons

Re: [whatwg] Default (informal) Style Sheet

Kempen, E.J.F. van wrote: What exactly are you looking for? Defining that 'normal' text is black by default and links are blue-ish? Because that's done already, most default styles are uniformly, but maybe informally, defined. > One example that springs to mind is that the default CSS rules

Re: [whatwg] on codecs in a 'video' tag.

Maciej Stachowiak wrote: We think your reasons are strong and worthy of respect. That is why we are not trying to force our codec preference on you, but rather propose to leave this issue open. We ask you to respect our reasons as well, rather than trying to force us to go along with your cod

Re: [whatwg] Full screen for the element

Gervase Markham wrote: Gareth Hay wrote: I think it should be like this, as you are telling the element to go fullscreen and *not* the page. That's my opinion. I guess that's the heart of it. My view is the opposite. I don't think video should be special in this regard. If you want to see

Re: [whatwg] Full screen for the element

Gervase Markham wrote: My assertion is that the idea of "going to full screen" (i.e. removing all chrome and allowing the content to take up as much space as possible) is a fairly common browser thing. Of course, those with a wider experience of browser implementations than I may well tell me

Re: [whatwg] Full screen for the element

Arve Bersvendsen wrote: > Note that 'fullscreen' and 'fullscreen' are two different things: > > 1. A fullscreen mode on desktop should typically be a paged media, > applying any 'projection' style sheets to the page > 2. The fullscreen mode on Sony Ericsson P990i, M600i and a number of > other

Re: [whatwg] , , Timed Media Elements -- Part I SMIL

ddailey wrote: On Thu, 22 Mar 2007 13:03:24, Anne van Kesteren wrote 1. why not just include SMIL as a part of HTML, much in the same way that it is integrated with SVG? It is an existing W3C reco. Reasons for not using were that it was 1) complicated and 2) not used. Thanks Anne... Is t

Re: [whatwg] Apple Proposal for Timed Media Elements

Gervase Markham wrote: Ian Hickson wrote: Biting off more than we can chew is a common mistake in Web specification development. lynx -dump -nolist http://www.whatwg.org/specs/web-apps/current-work/ | wc --words 143147 lynx -dump -nolist http://www.whatwg.org/specs/web-forms/current-wor

Re: [whatwg] Full screen for the element

Gervase Markham wrote: Simon Pieters wrote: Browsers are allowed to provide full screen, however there's no API for it. Entering fullscreen should only be under the control of the user, otherwise the author could hijack the user's screen and no way to get out of it (e.g. as soon as the user tr

Re: [whatwg] Codecs (was Re: Apple Proposal for Timed Media Elements)

Maciej Stachowiak wrote: - Even if all browsers end up supporting Ogg Theora/Vorbis, these are not the best-compression codecs available. So a large-scale video content provider that wants to save on bandwidth may wish to provide H.264/AAC content to those browsers that can handle it, even if

Re: [whatwg] Apple Proposal for Timed Media Elements

Maciej Stachowiak wrote: I think can use almost the exact same APIs for most things as . This has the nice side benefit that new Audio() can just make an element and provide all the relevant useful API. To me, the distinction between the element and the Audio object is that the former

Re: [whatwg] element feedback

Sander Tekelenburg wrote: Something else concerning first-class Netizenry: I'd like to see the spec to require UAs support implicit anchors, so that one can link to a specific startpoint: http://domain.example/movie.ogg#21:08>, to mean "fetch the movie and start playing it at 21 minutes 8 second

Re: [whatwg] element feedback

Gareth Hay wrote: This is a bit of a sideways step here, but why not make tags reflect MIME type, e.g. image/* video/* application/* audio/* That way we have a clear identification of what is going to be in the tag, API's can be tailored sufficiently for e

Re: [whatwg] Web Forsm 2.0 possible omissions

[EMAIL PROTECTED] wrote: 2) Auto tabbing for a 4 digit code: A more general request would be an ability to display one value but have a different one behind the scenes. Obviously when the user edits it they would expose the internal value, much like in an spreadsheet when you switch a fie

Re: [whatwg] element feedback

Ian Hickson wrote: A large portion of the feedback concerned the way that the current spec doesn't have any features for native browser-provided UI. I completely agree that on the long term this is something we need to offer. However, we musn't bite off more than we can chew. There are seve

Re: [whatwg] Video proposals

Vladimir Vukicevic wrote: If providing content in non-Theora formats is important, the client > should list the supported video formats in the Accept header, and the server can send back the right thing. [snip] Though as has been pointed out by someone else earlier in the thread, the MIME

Re: [whatwg] Comments on the element

Mihai Sucan wrote: For Youtube, a site which provides bloggers an easy way to integrate videos, this would prove even ... hard. Here's the simple code users have to copy/paste: http://www.youtube.com/v/id";> http://www.youtube.com/v/id"; type="application/x-shockwave-flash" wmode="transpa

Re: [whatwg] Attribute proposal:

Alexey Feldgendler wrote: Automatic behavior in HTML has been traditionally expressed through scripting. It's not hard to write a one-line script which automatically starts playback, but solutions based on scripting are easier to circumvent on the user side (and it's good). -1 for |autoplay

Re: [whatwg] Minor comments on

Anne van Kesteren wrote: * If the video is shown "letterboxes" what does the surrounding space look like? Would that be the 'background' of the element? Presumably the CSS "background" property would define the surrounding space. The pixels in that space would be treated the same way as

Re: [whatwg] versus xml:base

Asbjørn Ulsberg wrote: If it is, then when looking at links inside head, relative URIs are resolved using a base of "bar/foo/bar/" (taking [EMAIL PROTECTED]:base into account twice: once to resolve [EMAIL PROTECTED], which sets the document's base URI, and then relative to that base URI to reso

Re: [whatwg] Using the HTML5 DOCTYPE as a new quirksmode switch

Asbjørn Ulsberg wrote: Improving on the legacy, proprietary DOM just isn't feasible, imo. Are there particular parts that overlap between IE's DOM and the standard DOM where IE's implementation is non-compliant? If not, why can't IE simply support both sets of methods at the same time? (I

Re: [whatwg] Fallback behavior

Maciej Stachowiak wrote: As far as I can tell, the current spec does not adequately define how fallback behavior works. Specifically, what should be done with fallback content when not falling back? Presumably it should be parsed into the DOM, but should not render - that's the de facto beh

Re: [whatwg] element proposal

Lachlan Hunt wrote: Shadow2531 wrote: I think it'd be cool if the video element *just* supported theora. Mandating support for a single specific video format like Theora would be like requiring browsers to only support PNG for images. Sure, Theora has the major advantage of being (supposed

Re: [whatwg] element proposal

James Justin Harrell wrote: What is considered a "video format"? Would Flash or SVG be allowed? Given the structure of the API and the comparison to the Audio() functionality, I would take this to mean a continous, non-interactive audio/visual stream. Flash seems more like an "applet" tha

Re: [whatwg] X/HTML5 and DocBook

David Latapie wrote: Hello, I never used it, but a common complaint about DocBook is that there is too much tags. Now, considering how microformats seems to be the Next Big Thing™ (and we are talking quite a lot on this ML about this technology), could someone with a background in DocBook t

Re: [whatwg] several messages about HTML5

Benjamin Hawkes-Lewis wrote: James Graham wrote: Obviously I would love to be proven wrong but given the limited success in this field in the last decade, I'm not holding my breath. What actual attempts have been made in this field, that could be judged relative successes or failures? The b

Re: [whatwg] The m element

Geoffrey Sneddon wrote: On 8 Feb 2007, at 15:23, Leons Petrazickis wrote: In the Western world, the standard for highlighting is a neon yellow background. I submit that a much better name for is (, , ). People don't necessarily mark text much -- if anything, "mark" implies underlining, circl

Re: [whatwg] The m element

James Graham wrote: Leons Petrazickis wrote: They are marking the search terms with a highlighter. In an aural browser, would these terms be read differently? Perhaps. Does this transfer to mobile browsers? Very definitely. How would an auraul browser treak these terms differently? I can perha

Re: [whatwg] Problems with DOMTokenString

Maciej Stachowiak wrote: Alternative #2: leave the className an ordinary string, but add a new readonly DOMClassList classList property with something like the following interface: interface DOMClassList { void add(DOMString newClass); void remove(DOMString removeClass); bool has

[whatwg] WF2: Non-validating submit buttons

It would be useful to be able to mark certain submit buttons as non-validating. Use case: lots of the forms generated by one of my web-apps have a "Cancel" button which simply causes the server to redirect the user back to wherever they came from. When I use the WF2 extensions to mark requi

Re: [whatwg] xml:space

Anne van Kesteren wrote: xml:space can't affect the tree being formed as far as I know. It's not entirely clear to me what its use is anyway, except in SVG, where they defined it in a funny way to make it do something. Presumably its primary purpose is to act as a signal to generic XML to

Re: [whatwg] and

Henri Sivonen wrote: “Quotation” (Source) Or, if you're really keen on having some markup in there: Quotation (http://www.example.com/";>Example Source) and now a hypothetical interested tool can build a list of references at the end of the document. For example, one could produce a render

Re: [whatwg] and

Benjamin Hawkes-Lewis wrote: What are you guys talking about? You've got this exactly backwards: you don't consult online services to find out ISBNs (although you can); you use ISBNs to find books on online services. So do you expect browsers to use an online service to look up information a

Re: [whatwg] microformats incompatible with WebApps 1.0 ?

Mike Schinkel wrote: But you are assuming there is a downside to them for calling it "foo-name" vs. just "name." There isn't; developers use conventions all the time. And if you read my proposal clearly, the prefix is only needed on a top-level element or to disambiguate. I'm not sure if yo

Re: [whatwg] Inline SVG

Michel Fortin wrote: Le 8 déc. 2006 à 15:20, Leons Petrazickis a écrit : Unlike Michel Fortin's proposal for , I suggest that SVG included like this be rendered as an image in that exact spot. We may want

Re: [whatwg] PaceEntryMediatype

Ian Hickson wrote: Then the browser wouldn't take these links and make them available in a "list of feeds" interface, which is the problem we are trying to solve. Why is it useful for a browser to make a list of a bunch of random feeds that have no relation to one another or to the current

Re: [whatwg] several messages about XML syntax and HTML5

Alexey Feldgendler wrote: LiveJournal, a popular blogging service, inserts hand-authored content into hand-authored templates. While the templates are written by competent authors who (mostly) know how to write proper HTML, blog posts are most often written by people who barely learnt how to

Re: [whatwg] PaceEntryMediatype

Alexey Feldgendler wrote: On Wed, 06 Dec 2006 22:42:06 +0600, Ian Hickson <[EMAIL PROTECTED]> wrote: In your example, what's the relation between status.xml and this page? status.xml is just a resource that provides a syndication feed. It is not necessarily associated with a p

Re: [whatwg] Graceful Degradation and Mime Types[was: trailing slash]

Mike Schinkel wrote: All really sucessful text formats have been easy to edit (why did RSS take off while RDF is still struggling to get off the ground?) > I don't necessarily disagree with your sentiment, but it could be argued that RSS has done well while RDF has floundered largely because

Re: [whatwg] several messages about XML syntax and HTML5

Sam Ruby wrote: [snip] HTML5 can do one better. Instead of handling presentational MathML as a special case, this support can be generalized. When a non-HTML element is encountered inside a HTML document, the parser could make one additional check: does this attribute have a xmlns attribute d

Re: [whatwg] several messages about XML syntax and HTML5

Elliotte Harold wrote: What you keep missing is, it's not just about browsers. Not all clients are classic web browsers. The same documents are sent to many different kinds of clients that do many different things. I need to pass well-formed XML to my non-browser tools, and readable HTML to c

Re: [whatwg] several messages about XML syntax and HTML5

Michel Fortin wrote: I think xmlns="http://www.w3.org/1999/html"; is fine in HTML because it just states what is already implied. That's fine as long as other values of xmlns are invalid. My understanding of the discussion so far has basically been to allow this attribute but completely disre

Re: [whatwg] HTML5 Edit Link Relation (was: PaceEntryMediatype)

Robert Sayre wrote: While "type" is useful for things which result in GET requests, while specifying several locally-relevant protocols I've run into the fact that it's not so hot for anything that requires the client to include an entity body in the request, or requires any other reques

Re: [whatwg] HTML syntax: shortcuts for 'id' and 'class' attributes

Andrew Fedoniouk wrote: | > | > ... is equivalent of | > ... | > | | HTML5 is meant to be backwards compatible, so this is out of the question. And where do you see problems with backward compatibility? Or let's put this way: what would be a definition of backward compatibility in terms of HTML

Re: [whatwg] Still beating the drawString() dead horse...

Stefan Haustein wrote: Everything beyond is a separate use case that should be discussed separately. I think the main problem here is that drawElement() was suggested as a kind of replacement for drawString(), but it is actually something completely different, that should be discussed separat

Re: [whatwg] Still beating the drawString() dead horse...

Stefan Haustein wrote: Hi, I have tried to sum up the requirements for CanvasRenderingContext2D.drawString() at http://rhino-canvas.sf.net/www/drawstring.html The page contains an API proposal based on the Font/TextStyle object approach that meets all those requirements, and also some motiva

Re: [whatwg] Footnotes, endnotes, sidenotes

Elliotte Harold wrote: Matthew Paul Thomas wrote: Scholarly books sometimes use both footnotes and endnotes for different things -- footnotes for citations and endnotes for tangential discussions, or vice versa. I've never seen an HTML document try to make this distinction, though. Distin

Re: [whatwg] Scoped tabindex proposal

Simon Pieters wrote: Then it would be better to drop the tabindex="scoped" idea and instead define that any tabindex element is a scoping element, so you would use tabindex="1" on #container2 and tabindex="2" on #container1. I think this makes more sense than changing tabIndex to a DOMString,

Re: [whatwg] Scoped tabindex proposal

Simon Pieters wrote: So here's an idea. A new value for the tabindex attribute, "scoped". Here's an example: The following links should be focused in the order which the link text indicates: first second forth third fifth last The table itself is not in

Re: [whatwg] Mathematics on HTML5

[originally sent privately by mistake; sorry Ian.] Ian Hickson wrote: > On Wed, 7 Jun 2006, Mihai Sucan wrote: > >> Yes, it's true authors don't generally jump on whatever comes new (that's the reason MathML is not as widely used as LaTeX). > > > > I would say MathML is not widely used because

  1   2   >