Re: [whatwg] Accessing local files with JavaScript portably and securely

On 18 April 2017 12:18:57 BST, duanyao wrote: >在 2017年04月18日 18:52, Ashley Sheridan 写道: >> >>> Maybe no. "files" is a generic word, so if you make every >"xxx_files/" >>> folders magical, it's quite possible that there are folders happe

Re: [whatwg] Accessing local files with JavaScript portably and securely

>Maybe no. "files" is a generic word, so if you make every "xxx_files/" >folders magical, it's quite possible that there are folders happen to >ends with "_files" but are not intented to be local web apps. If you >require a `xxx.html` to make "xxx_files/" magical, it is a little >awkward and

Re: [whatwg] sticky css hover state on touch devices

On 6 December 2016 05:24:59 GMT+00:00, Zac Spitzer wrote: >on touch devices, there is a problem with sticky hover states > >https://bugs.webkit.org/show_bug.cgi?id=158517 >https://bugs.chromium.org/p/chromium/issues/detail?id=370155 > >one workaround it to clone, remove and re-insert the elemen

Re: [whatwg] Proposal for showing thousand separator in form controls.

On 14 October 2015 10:47:43 BST, "Михаил Гаврилов" wrote: >2015-10-14 0:41 GMT+05:00 Boris Zbarsky : >> See https://bugzilla.mozilla.org/show_bug.cgi?id=974175 for details. > >I think the problem with the display of the year with the help of > far-fetched. Sooner or later year will >be five-dig

Re: [whatwg] Proposing: "autoscroll" event

I thought the point was that the JavaScript event would fire before the scroll, which would allow you to cancel the default action, no? "Tab Atkins Jr." wrote: >On Tue, May 14, 2013 at 2:31 PM, Nils Dagsson Moskopp > wrote: >> Kyle Simpson schrieb am Tue, 14 May 2013 16:08:17 >> -0500: >>> The

Re: [whatwg] Menus and Toolbars

There is a hack that allows css to handle clicks using hidden checkboxes and adjacent :checked siblings. Its not terribly suited for menu-type behavior though. Fred Andrews wrote: >Dear Ian, > >Thank you opening a discussion about these interactive elements. It >would be disappointing to see

Re: [whatwg] Features for responsive Web design

On Sat, 2012-10-13 at 06:04 +, Fred Andrews wrote: > > > From: m...@apple.com > ... > > > My point is, that any device-specific notation, such as "2x", forces the > > > author to make decisions that the browser should actually make. The > > > author does not know if in a few years the image

Re: [whatwg] "content" element, which we need in our documents

Ian Yang wrote: >Hi editors in chief and everyone else, > >How have you been recently? > >As many of you may have been aware that there is an important >sectioning >element we have been short of for a long time: the "content" element. > >Remember how we sectioned our documents in those old days

Re: [whatwg] communicating plugin state (primarily for click-to-play)

On Tue, 2012-06-12 at 13:18 -0700, Peter Kasting wrote: > On Tue, Jun 12, 2012 at 1:07 PM, Glenn Maynard wrote: > > > On Tue, Jun 12, 2012 at 1:22 PM, Peter Kasting wrote: > > > >> The "temporary" implementation > >> should probably be along the lines of "reload the page, this time allowing > >>

Re: [whatwg] Caching of identical files from different URLs using checksums

Ian Hickson wrote: >On Fri, 17 Feb 2012, Sven Neuhaus wrote: >> Hello, >> >> as of 2012, some websites are including popular javascript libraries >from CDNs, like >> Google's. The benefits are: >> >> * Traffic savings for the site operator because the javascript >libraries are downloaded from >

Re: [whatwg] Bandwidth media queries

On Wed, 2012-05-16 at 20:09 +0100, Matthew Wilcox wrote: > Ok, so really it's an efficiency of authoring problem; before I just > didn't get how it'd be any different to a viewport width from the > perspective of an author. > > That said, when coupled with viewport responses... yeah, that could >

Re: [whatwg] runat (or "server") attribute

On Sun, 2012-05-13 at 17:16 +0200, Anne van Kesteren wrote: > Just use type="text/server-js"... > > Is that really a good idea? It seems odd to use a mime type for such a reason. > -- > Anne van Kesteren > http://annevankesteren.nl/

Re: [whatwg] Implementation complexity with elements vs an attribute (responsive images)

> > > > Also note that there is a great difference in implementation complexity > > between various properties above. For example, viewport width/height is > > rather easy to work with because one can assume it won't change between > > prefetching and layout, so one can prefetch the right asset. O

Re: [whatwg] Allow empty string for input type=color

On Fri, 2012-05-04 at 04:33 +1000, Shaun Moss wrote: > The way things are done is not always the best way. Most colour pickers > are used in instances where "not selected" would make no sense. > > However, as you're designing a widget for the web that may be used by > billions of people in any

Re: [whatwg] Double meaning of the element

On Wed, 2012-05-02 at 11:31 +1000, Shaun Moss wrote: > I know it's contentious, but as a teacher it's very simple to teach > students of HTML5 that: > = underline > = bold > = italic > = strikethrough > > Of course, I also teach and , but the simplest way to teach > and is that it's mere

Re: [whatwg] multipart/form-data filename encoding: unicode and special characters

On Tue, 2012-05-01 at 21:12 -0400, Evan Jones wrote: > I am not an experienced web standards wonk, so please forgive me if I'm > making a mistake here. > > When uploading files that contain special characters in their name, it > appears to me that it is unspecified as to how those file names sh

Re: [whatwg] Caching of identical files from different URLs using checksums

On Fri, 2012-02-17 at 19:05 +0100, Julian Reschke wrote: > On 2012-02-17 09:42, Sven Neuhaus wrote: > > Hello, > > > > as of 2012, some websites are including popular javascript libraries from > > CDNs, like > > Google's. The benefits are: > > > > * Traffic savings for the site operator because t

Re: [whatwg] The blockquote element spec vs common quoting practices

>> Riveting tale, chap. Can you provide proof? > >Actually the burden of proof is on those who think that >has >some useful support. No, that's not how burden of proof works. You made a claim regarding blockquote, nils asked for proof. The onus is on you. Thanks, Ash http://ashleysheridan.co

Re: [whatwg] add html-attribute for "responsive images"

On Tue, 2012-02-07 at 10:56 +, Bjartur Thorlacius wrote: > On 2/7/12, Ashley Sheridan wrote: > > The main problem I see with that is that the tag doesn't have > > the same accessibility attributes, so you'd effectively lock out a lot > > of people using bro

Re: [whatwg] add html-attribute for "responsive images"

media-xl="(min-device-width:1024px)" > media-src-xl="myimage_xsl.jpg"> > (View as gist: https://gist.github.com/1158855) > > Or did I misunderstood you? > -Anselm > > Am 07.02.2012 um 10:45 schrieb Ashley Sheridan: > > > On Mon, 2012-02-06 at 23:

Re: [whatwg] add html-attribute for "responsive images"

On Mon, 2012-02-06 at 23:15 +, Bjartur Thorlacius wrote: > On Mon, 06 Feb 2012 21:23:37 -, Mathew Marquis > wrote: > > I recently published a sum-up of our thinking at A List Apart ( > > http://www.alistapart.com/articles/responsive-images-how-they-almost-worked-and-what-we-need/ > >

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header (Boris Zbarsky)

On Mon, 2012-02-06 at 22:16 +, Kornel Lesiński wrote: > On Mon, 06 Feb 2012 20:00:45 -, Irakli Nadareishvili > wrote: > > > 1. Adaptive images: > > To optimize user-experience on smart-phones (most of which have > > relatively small screens, and are on slow connections most of the ti

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header

On Mon, 2012-02-06 at 13:59 -0500, Boris Zbarsky wrote: > On 2/6/12 1:55 PM, Bjartur Thorlacius wrote: > > On Mon, 06 Feb 2012 17:44:30 -, Boris Zbarsky wrote: > >> Yes, indeed. "Supports touch input on multiple spots at once" vs > >> "supports only a mouse" seems like a much more important d

Re: [whatwg] RWD Heaven: if browsers reported device capabilities in a request header

On Mon, 2012-02-06 at 13:58 -0500, Boris Zbarsky wrote: > On 2/6/12 1:55 PM, Irakli Nadareishvili wrote: > > Many thanks to everybody who has responded and for a lively and a > > productive discussion! > > > > Quick clarification: the proposal is to include *device* capabilities in > > the HTTP

[whatwg] Use of media queries to limit bandwidth/data transfer

I couldn't find anything about this specifically, and I'm not sure if this is the best place to ask this, but here we go. I've been trying to optimise my site (as a test case) for mobile usage and one area where I found issues was with the media queries used to link CSS files. I noticed that despi

Re: [whatwg] New attributes would degrade better than new elements

On Sat, 2011-10-29 at 16:38 +0300, Jukka K. Korpela wrote: > Can you please now do me, and others, a favor and give some evidence of > actual Google behavior in this respect? If it's something that we need > to be aware of, it should be observable from outside Google, i.e. when > using Google,

Re: [whatwg] New attributes would degrade better than new elements

"Jukka K. Korpela" wrote: >27.10.2011 9:55, Ashley Sheridan wrote: > >>> There is no _required_ functionality or default rendering for >or >>> and no special attributes for them. What you lose by >having >>> them as elements rather than a

Re: [whatwg] New attributes would degrade better than new elements

On Thu, 2011-10-27 at 09:28 +0300, Jukka K. Korpela wrote: > 27.10.2011 5:38, Eric Sh. wrote: > > > And if we stop adding new features old browsers do not support or not use > > them because very little browsers are not supporting them then it would > > completely stop innovation and the evolutio

Re: [whatwg] New attributes would degrade better than new elements

On Thu, 2011-10-27 at 02:37 +0300, Jukka K. Korpela wrote: > 27.10.2011 0:57, Ashley Sheridan wrote: > > > If people are using versions of IE that old, then > > they deserve to have an older version of the "web" given to them. > > That's rather elitistic,

Re: [whatwg] New attributes would degrade better than new elements

On Thu, 2011-10-27 at 00:36 +0300, Jukka K. Korpela wrote: > 26.10.2011 23:16, Tab Atkins Jr. wrote: > > > Believe me, these discussions were had in the past. > > I do, but did you draw the conclusions? > > > All major UAs except old IE handle unknown elements in a way that's > > acceptable >

Re: [whatwg] New attributes would degrade better than new elements

On Thu, 2011-10-27 at 04:14 +0800, Kang-Hao (Kenny) Lu wrote: > (11/10/27 3:38), Jukka K. Korpela wrote: > > Nobody needs new elements with no required functionality, really. The > > idea of more compact markup is pointless. > > Every time I ask myself what the use cases of the semantic elements

Re: [whatwg] DOCTYPE declaration

On Sun, 2011-10-16 at 23:10 +0200, Nils Dagsson Moskopp wrote: > Boris Zbarsky schrieb am Sun, 16 Oct 2011 15:43:26 > -0400: > > > On 10/16/11 2:15 PM, Francis Boumphrey wrote: > > > My point is, as the only possible use for a DOCTYPE declaration in > > > HTML (any version) is for includingdecla

Re: [whatwg] (no subject)

On Wed, 2011-10-05 at 17:59 +, Ian Hickson wrote: > On Wed, 5 Oct 2011, Hamza dridi wrote: > > > > Hi , i have something in my mind and i thaught it would be better i tell > > you so excuse me if this is not the right place and excuse for my bad > > english so i've seen facebook using a plug

Re: [whatwg] HTML5 Site Headers

a page that is shown before being directed to the actual > site content - usually with a very limited amount of info. > > Kevin > > > On Thu, Sep 15, 2011 at 10:50 AM, Ashley Sheridan > wrote: > > > I'd say yes, wherever you can look at something and say that

Re: [whatwg] HTML5 Site Headers

I'd say yes, wherever you can look at something and say that's the header for something. I'm not sure about your meaning of a splash page though... Thanks, Ash http://www.ashleysheridan.co.uk -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. "Kevin A. Cameron" wrote: Is is

Re: [whatwg] add html-attribute for "responsive images"

On Tue, 2011-09-06 at 07:15 +0200, Karl Dubost wrote: > Le 5 sept. 2011 à 15:07, Anselm Hannemann - Novolo Designagentur a écrit : > > Why should we use inline-styles once again? Why should we load content > > images with CSS? What about accessibility? Where to add alt-attribute / > > title / AR

Re: [whatwg] Video- and audio-controls without scripting

Timo Beermann wrote: >The new video- and audio-tag are great, but the controls (play/pause, >skip forward, skip back, volume, progress bar, time) should be >possible without scripting. Some standard-controls that also can be >modified with CSS. Because some users deactivate Scripting (for >secu

Re: [whatwg] Selectors within

On Wed, 2011-07-20 at 20:36 +0100, Kornel Lesiński wrote: > On Tue, 19 Jul 2011 05:14:55 +0100, Boris Zbarsky wrote: > > > This is actually an interesting question. Does this end up > > corresponding to: > > > >:scope foo .bar, foo:scope .bar > > > > or to just > > > >:scope foo .bar

Re: [whatwg] onForward and onBackward event and enable/disable Forward and Backward buttons.

On Sat, 2011-04-16 at 11:12 -0400, Biju wrote: > Hi, > >setInterval(function(){location='#'+(1*new Date())},0) > > At least in Firefox 4 above code make entire history filled with > current url with different hash. > And hence already now a website can make Backward/Forward button useless. >

Re: [whatwg] microformats, microdata, and custom data attributes

On Fri, 2011-04-15 at 22:12 -0700, Tab Atkins Jr. wrote: > On Fri, Apr 15, 2011 at 6:29 PM, Justin Karneges wrote: > > Hi folks, > > > > I'm desiring a way to markup "mentions of a person" semantically within > > HTML, > > for use in an open standard. Think of a more rich form of the @person >

Re: [whatwg] Interpretation issue: can be used for "extended

On Tue, 2011-03-15 at 19:47 +0100, Jacob Kristensen wrote: > Why would anyone want to include lists inside paragraphs? > Aside from those very old, ancient documents/sites that are left out there, > who left out the closing tags for paragraphs? > > Where you would typically see one large paragra

Re: [whatwg] Giving the tag a new meaning.

a problem. Former has never been a problem, web > as worked well in that way. I just am setting out a new way of thinking > about html. Being more declarative. > > 2011/3/1 Ashley Sheridan > > > On Tue, 2011-03-01 at 12:32 -0800, Tab Atkins Jr. wrote: > > > > On Tue

Re: [whatwg] Giving the tag a new meaning.

On Tue, 2011-03-01 at 12:32 -0800, Tab Atkins Jr. wrote: > On Tue, Mar 1, 2011 at 12:09 PM, usuario wrote: > > The real issue is with change, never is too late. > > Many of the new elements in html5 are for semantic purposes. Being now a > > and a , there is only one left thing that's pretty obv

Re: [whatwg] wrapper element

On Mon, 2011-02-28 at 18:46 +, usuario wrote: > [Had problems sending my mails to the list, resending message] > > Some of you may be questioning why a wrapper element if it has not > semantics, the thing is, It DO have semantics. > > Wrapper: > a container element whose solely purpose is to

Re: [whatwg] navigation shouldn't abort if canceled

"Boris Zbarsky" wrote: >On 2/2/11 3:22 PM, Michael Nordman wrote: >> That does sound like a bug? I'd be curious to know what the reasoning >> was for the existing sequence of steps. > > From what I can tell, current browser behavior. > >> Step 10 looks out of place too... >> >> "10. If the new re

Re: [whatwg] New method for obtaining a CSS property

"Boris Zbarsky" wrote: >On 1/28/11 1:22 AM, Brett Zamir wrote: >> My point is that a selector can be tied to a property through the >> ruleset. > >No, not really. Something that _matches_ selectors an be tied to a >property via seeing which selectors it matches and then considering the > >result

Re: [whatwg] New method for obtaining a CSS property

"Boris Zbarsky" wrote: >On 1/27/11 4:48 AM, Brett Zamir wrote: >> I was thinking of it grabbing the "winning" property for the whole >> document, i.e., the one which would be applicable without knowing >more >> contextual information. So, if the selector specified were ".error", >it >> wouldn't

Re: [whatwg] element in HTML5 Spec?

On Mon, 2010-12-13 at 12:33 -0800, Tab Atkins Jr. wrote: > On Mon, Dec 13, 2010 at 12:06 PM, Ashley Sheridan > wrote: > > Would be more contextually accurate in the case of user-generated > > comments? I was of the understanding that elements were content > > that

Re: [whatwg] element in HTML5 Spec?

On Mon, 2010-12-13 at 19:54 +, Benjamin Hawkes-Lewis wrote: > On Mon, Dec 13, 2010 at 6:49 PM, Richard Summers > wrote: > > I was > > wondering, is there any plan to implement a element within the > > HTML5 spec? > > "comment" isn't an available element name for historical reasons: > > htt

Re: [whatwg] element "img" with HTTP POST method

On Thu, 2010-12-09 at 11:01 -0800, Adam Barth wrote: > We've seen use cases for a similar feature for iframes and hyperlinks. > For example: > > Logout > > would be more semantically correct that just href="/logout">Logout because it would generate a POST instead of > a GET. > > Adam > > >

Re: [whatwg] Exposing spelling/grammar suggestions in

On Mon, 2010-11-29 at 10:40 -0800, Charles Pritchard wrote: > > Date: Sun, 28 Nov 2010 15:54:04 +0100 > > From: Christoph P?per > > To: whatwg group > > Subject: Re: [whatwg] Exposing spelling/grammar suggestions in > > contentEditable > > Message-ID:<62959690-0e26-4bbc-ab4f-f9726f24c...@criss

Re: [whatwg] Exposing spelling/grammar suggestions in contentEditable

On Sun, 2010-11-28 at 11:27 +0200, timeless wrote: > On Sat, Nov 27, 2010 at 10:19 PM, Charles Pritchard wrote: > > Is there room for discussion of an API > > there's room to discuss such things. > > > to expose misspelled ranges of text in contentEditable? > > I'm worried about privacy risks.

Re: [whatwg] without keyboard editing

On Mon, 2010-11-01 at 06:15 +0200, timeless wrote: > On Mon, Nov 1, 2010 at 4:31 AM, TAMURA, Kent wrote: > > A team in Google tried to use for a product, and they > > decided > > not to use it. > > > What they needed was a control to select an integer from a specific integer > > range > > such

Re: [whatwg] Suggested enhancement for initialization of mouse events

On Tue, 2010-09-14 at 07:51 -0400, Jim Williams wrote: > Currently, there appears to be no way of sensing the location of the > mouse cursor without waiting for user-initiated events. The problem > is that there is no way to fill in the real current values for many of > the parameters when execut

Re: [whatwg] element feedback

On Tue, 2010-08-31 at 16:09 -0400, Aryeh Gregor wrote: > On Tue, Aug 31, 2010 at 3:53 PM, Ashley Sheridan > wrote: > > I think localisation does have a valid use though. Consider a page written > > in English with the date 01/12/2010. Is that date the 1st December, or the >

Re: [whatwg] element feedback

On Tue, 2010-08-31 at 15:40 -0400, Aryeh Gregor wrote: > On Tue, Aug 31, 2010 at 5:25 AM, Martin Janecke wrote: > > Besides, 2010 in a British news article would allow users e.g. > > in Japan to have these dates displayed as 平22年. That's clearly an advantage > > over the number 2010 alone. > > I

Re: [whatwg] select element should have a required attribute

On Tue, 2010-08-10 at 11:35 +0200, Mounir Lamouri wrote: > On 08/10/2010 07:09 AM, Garrett Smith wrote: > >> Many times you want the user to make an explicit choice, rather than > >> just leaving whatever was already selected. What many websites do is: > >> > >> Choose an option: > >> > >>

Re: [whatwg] select element should have a required attribute

On Mon, 2010-08-09 at 16:54 -0700, Jonas Sicking wrote: > On Mon, Aug 9, 2010 at 4:35 PM, Ian Hickson wrote: > > On Fri, 18 Jun 2010, Mounir Lamouri wrote: > >> > >> I'm wondering why select element do not have a required attribute. > > > > It's impossible to submit a element (without a size=""

Re: [whatwg] [br] element should not be a line break

On Mon, 2010-08-09 at 11:55 +0200, Thomas Koetter wrote: > Aryeh wrote: > >No, but it's a stand-in for a class of semantics that can only fairly > >be summarized as "the places where you would always use a line break > >in print". There is no single behavior that screen readers could use > >to co

Re: [whatwg] and links with @rel=embed

On Fri, 2010-08-06 at 12:43 -0700, Tab Atkins Jr. wrote: > On Thu, Aug 5, 2010 at 7:43 PM, Bjartur Thorlacius > wrote: > > On 8/5/10, Tab Atkins Jr. wrote: > >> I'll note, though, that that isn't a very useful pattern for users in > >> the first place. Most users won't have any idea what to do

Re: [whatwg] Please consider simplifying authoring guidance for the alt attribute

On Tue, 2010-08-03 at 11:58 +0200, Markus Ernst wrote: > Am 02.08.2010 20:54 schrieb Ashley Sheridan: > > On Mon, 2010-08-02 at 17:19 +0200, Markus Ernst wrote: > >> - search engines should generally ignore text in the alt attribute, but > >> evaluate

Re: [whatwg] Please consider simplifying authoring guidance for the alt attribute

On Mon, 2010-08-02 at 17:19 +0200, Markus Ernst wrote: > - search engines should generally ignore text in the alt attribute, > but > evaluate the title attribute instead > > Rationale: > > 4.8.1.1.12 says: "A corollary to this is that the alt attribute's > value > should never contain text tha

Re: [whatwg] "Content-Disposition" property for tags

On Mon, 2010-08-02 at 18:09 +0200, Dennis Joachimsthaler wrote: > Ben Schwarz wrote: > > > I'm really not too sure what pre-existing problem this actually solves. > > Given that a server sets the correct mime-types for a given resource, we > > know what "type" it is already. > > Yes, since we d

Re: [whatwg] Article: Growing pains afflict HTML5 standardization

On Sat, 2010-07-10 at 20:31 +0100, Diogo Resende wrote: > I hate it. > > > > > From: whatwg-boun...@lists.whatwg.org > [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Schalk Neethling > Sent: sábado, 10 de Julho de 2010 18:54 > To: wha...@whatwg.org > Subject: [whatwg] Article: Growing p

Re: [whatwg] HTML5 (including next generation additions still in development) - Mozilla Firefox (Not Responding)

On Thu, 2010-07-08 at 19:18 +0200, Diego Perini wrote: > > > > On Thu, Jul 8, 2010 at 4:03 PM, Lachlan Hunt > wrote: > > On 2010-07-08 02:28, Garrett Smith wrote: > > This is about the fourth time I've said it here. Can > the person in >

Re: [whatwg] Iframe dimensions

On Tue, 2010-07-06 at 16:17 -0400, Aryeh Gregor wrote: > On Tue, Jul 6, 2010 at 6:49 AM, Markus Ernst wrote: > > My problem is this sentence in the spec for seamless: "This will cause links > > to open in the parent browsing context." > > > > In an application like http://test.rapid.ch/de/haendle

Re: [whatwg] More YouTube response

On Sun, 2010-07-04 at 23:56 +0100, David Gerard wrote: > On 4 July 2010 13:57, bjartur wrote: > > > I fail to see how BBC would be harmed by the usage of alternative > > software. Its business model is about content, not software, right? > > > See, you're using logic and sense ... about half t

Re: [whatwg] Technical Parity with W3C HTML Spec

On Fri, 2010-06-25 at 16:11 -0700, Tab Atkins Jr. wrote: > On Fri, Jun 25, 2010 at 4:00 PM, Mike Shaver wrote: > > On Fri, Jun 25, 2010 at 3:30 PM, Aryeh Gregor > > wrote: > >> I'm pretty sure they won't be. Any significant implementer has always > >> had veto power over the spec. > > > > I fe

Re: [whatwg] input type="location" proposals

On Fri, 2010-06-25 at 17:09 -0400, Aryeh Gregor wrote: > On Thu, Jun 24, 2010 at 8:55 PM, Ashley Sheridan > wrote: > > I think it's quite a fringe case. What about things that are more used: > > > > * type=number - a browser could aid input with some sort of spinner

Re: [whatwg] Allowing ">" in attribute values

On Fri, 2010-06-25 at 13:28 +0100, Kornel Lesinski wrote: > > A agree disallowing ">" chars in attributes greatly simplifies parsing. Not > > only with regular expressions, but any parsing. > > If ">" are allowed, it means that in order to found the end of the element > > you do have to read all a

Re: [whatwg] input type="location" proposals

On Thu, 2010-06-24 at 19:30 -0400, Eitan Adler wrote: > > > > Seeing your 2c and raising you a "citation needed." ;-) > > > > But to the point at hand > > > > Would the @pattern attribute cover the use case of lat/long inputs? (albeit > > without a nice UI) > > Possibly. I personally think

Re: [whatwg] Allowing ">" in attribute values

On Thu, 2010-06-24 at 09:01 -0700, Tab Atkins Jr. wrote: > On Thu, Jun 24, 2010 at 8:20 AM, Benjamin M. Schwartz > wrote: > > On 06/24/2010 11:04 AM, Kornel Lesinski wrote: > >> If you mean "parsing" with regular expressions, then I think that's a bad > >> practice and shouldn't be encouraged. >

Re: [whatwg]

On Sun, 2010-06-20 at 21:06 -0400, Gregory Maxwell wrote: > On Sun, Jun 20, 2010 at 8:23 PM, Nils Dagsson Moskopp > wrote: > > AFAIK, at least Firefox shows a fullscreen option already in the context > > menu. What makes you think there is another attribute needed (besides > > @controls) ? > > S

Re: [whatwg]

On Sun, 2010-06-20 at 22:13 +0100, Shane Fagan wrote: > On Sun, 2010-06-20 at 16:07 -0500, Mike Wilcox wrote: > > >>On Mon, 8 Mar 2010, balachandar muruganantham wrote:> > > >> I have heard from people that there have been a discussion on > > supporting > > >> the fullscreen mode for HTML5 video

Re: [whatwg] select element should have a required attribute

On Fri, 2010-06-18 at 13:34 -0700, Garrett Smith wrote: > On 6/18/10, Garrett Smith wrote: > > On 6/18/10, Ashley Sheridan wrote: > >> On Fri, 2010-06-18 at 11:35 +0200, Mounir Lamouri wrote: > >> > > [...] > > > > Implementations vary on act

Re: [whatwg] select element should have a required attribute

On Fri, 2010-06-18 at 13:03 -0400, Eitan Adler wrote: > > > On Fri, Jun 18, 2010 at 12:58 PM, Gordon P. Hemsley > wrote: > > I'm not sure how you interpreted, but I wanted to clarify, in > case it wasn't clear. > > I'm pretty sure this person is asking why @req

Re: [whatwg] select element should have a required attribute

On Fri, 2010-06-18 at 11:35 +0200, Mounir Lamouri wrote: > Hi, > > I'm wondering why select element do not have a required attribute. It > seems to be perfectly suitable. With the required attribute, select > element would be able to suffer from being missing and the :required > pseudo-class coul

Re: [whatwg] idea about html code security anti xss

On Wed, 2010-06-16 at 13:33 +0200, gabme...@westweb.at wrote: > On 6/15/10 6:19 PM, gabme...@westweb.at wrote: > Hello, > > I had just this idea after reading so much about xss and code injection. > > I think there is a simple solution: > > 1.) > I now invent an attribute called strlen=""

Re: [whatwg] idea about html code security anti xss

On Wed, 2010-06-16 at 03:19 +0200, gabme...@westweb.at wrote: > Hello, > > I had just this idea after reading so much about xss and code injection. > > I think there is a simple solution: > > 1.) > I now invent an attribute called strlen="" > > I append this to a htmlcode with strlen of 94843

Re: [whatwg] Is there a way to stop scrolling when pressing directional arrows?

istracts > me from the game. > > With that being said, Bespin (from Mozilla Labs) uses , and it > has no problem stealing the keyboard focus (with JavaScript) for most > keypresses. > > Gordon > > > 2010/6/14 Ashley Sheridan > > On Mon, 2010-06-14 at

Re: [whatwg] Is there a way to stop scrolling when pressing directional arrows?

On Mon, 2010-06-14 at 13:38 -0600, Carlos Andrés Solís wrote: > Hello! I've been noticing a problem in many HTML5 test apps, very > especially games. When the directional arrow buttons are pressed, the > screen scrolls. This is a problem that, as far as I know, Flash had > solved by changing the f

Re: [whatwg] Syntax highlighting language attribute for editable elements

On Sun, 2010-06-13 at 13:57 +0800, Brett Zamir wrote: > Has thought been given to allow textarea, input and/or contenteditable > elements to use an attribute (maybe like does with > class=language-XX) so that user agents might be able to display the > editable text with syntax highlighting cod

Re: [whatwg] audio and video: volume and muted as content attributes?

On Thu, 2010-06-10 at 12:32 +1000, Silvia Pfeiffer wrote: > On Thu, Jun 10, 2010 at 12:13 PM, Ashley Sheridan > wrote: > > > On Thu, 2010-06-10 at 12:03 +1000, Silvia Pfeiffer wrote: > > > On Thu, Jun 10, 2010 at 11:55 AM, Ashley She

Re: [whatwg] audio and video: volume and muted as content attributes?

On Thu, 2010-06-10 at 12:03 +1000, Silvia Pfeiffer wrote: > On Thu, Jun 10, 2010 at 11:55 AM, Ashley Sheridan > wrote: > > > On Thu, 2010-06-10 at 11:52 +1000, Silvia Pfeiffer wrote: > > > I don't think that is possible in the

Re: [whatwg] audio and video: volume and muted as content attributes?

On Thu, 2010-06-10 at 11:52 +1000, Silvia Pfeiffer wrote: > I don't think that is possible in the way that the volume attribute is > currently defined as a value between [0;1]. That is an orthogonal, but > still important question about the volume attribute then. > > So, if you say 300%, I assume

Re: [whatwg] input type=upload (not just files) proposal

On Tue, 2010-06-08 at 11:13 -0400, Mike Shaver wrote: > On Tue, Jun 8, 2010 at 11:02 AM, Ashley Sheridan > wrote: > > Yes, and the rest of my email said that. > > > Sorry, I am not familiar with KIO, and didn't see the need for OS > support. >

Re: [whatwg] input type=upload (not just files) proposal

On Tue, 2010-06-08 at 10:58 -0400, Mike Shaver wrote: > On Tue, Jun 8, 2010 at 10:47 AM, Ashley Sheridan > wrote: > > > On Tue, 2010-06-08 at 10:37 -0400, Simpson, Grant Leyton > wrote: > > > Are you wanting the user to

Re: [whatwg] input type=upload (not just files) proposal

On Tue, 2010-06-08 at 10:37 -0400, Simpson, Grant Leyton wrote: > Are you wanting the user to manually enter the filename, including the > file:// scheme? If not, are you envisioning the file dialog box to provide a > choice between selecting local files and entering an http/ftp url? > > On Jun

Re: [whatwg] bubbling events on labels

On Fri, 2010-06-04 at 15:21 -0700, Tab Atkins Jr. wrote: > On Fri, Jun 4, 2010 at 2:58 PM, Diego Perini wrote: > > I have different behavior in browsers with the "checked" state of a checkbox > > input element. > > > > I have filed a ticket in Webkit and I am looking after some > > advice/suggest

Re: [whatwg] 'Main Part of the Content' Idiom

On Fri, 2010-06-04 at 14:47 -0700, Tab Atkins Jr. wrote: > On Fri, Jun 4, 2010 at 1:32 PM, Ashley Sheridan > wrote: > > On Fri, 2010-06-04 at 13:28 -0700, Tab Atkins Jr. wrote: > > All browsers that you could possibly care about (any FF, Safari, > > Chrome, Opera, or

Re: [whatwg] 'Main Part of the Content' Idiom

On Fri, 2010-06-04 at 13:28 -0700, Tab Atkins Jr. wrote: > On Fri, Jun 4, 2010 at 1:16 PM, Roger Hågensen wrote: > > On 2010-06-04 22:03, Tab Atkins Jr. wrote: > >> > >> On Fri, Jun 4, 2010 at 12:58 PM, Roger Hågensen > >> wrote: > >>> > >>> ... > >>> As you can see the aside is outside the body

Re: [whatwg] 'Main Part of the Content' Idiom

content. It s a > pedagogical issue, where authors not too concerned with standards > compliance, should have an easy escape of at least defining the most > important on the site. > > > Thanks > /Daniel > > > > > > > > On Fri, Jun 4, 2010 at 5:1

Re: [whatwg] 'Main Part of the Content' Idiom

anks > /Daniel > > > On Fri, Jun 4, 2010 at 4:37 PM, Ashley Sheridan > wrote: > > > On Fri, 2010-06-04 at 16:27 +0200, Daniel Persson wrote: > > > I am the one posting the question on the help list. To me, > > the

Re: [whatwg] 'Main Part of the Content' Idiom

On Fri, 2010-06-04 at 16:27 +0200, Daniel Persson wrote: > I am the one posting the question on the help list. To me, the lack of > html5 definition of main content, ie body copy in paper publishing, is > a big mistake. Imagine the amount of sites where "everything else" > includes a lot of unimpo

Re: [whatwg] Form validation against invisible controls

On Thu, 2010-06-03 at 08:54 -0700, Tab Atkins Jr. wrote: > On Thu, Jun 3, 2010 at 8:42 AM, João Eiras wrote: > > On Thu, 03 Jun 2010 16:16:00 +0100, TAMURA, Kent wrote: > > > >> > >> > >>> > An element is a "candidate for constraint validation" if > >>> > 1. it is a validatable type, > >>> >

Re: [whatwg] Why there is no wrap="off", intentional or forgotten?

On Wed, 2010-06-02 at 12:51 +0200, Oldřich Vetešník wrote: > Hi, > > I'm missing the wrap="off" value for textarea wrap attribute; is there any > particular reason why this is not part of HTML5? > Currently the only values mentioned are "soft" and "hard": > > http://dev.w3.org/html5/spec/the-b

Re: [whatwg] Problem with http://www.webmproject.org/

On Thu, 2010-05-27 at 11:12 -0400, Michael A. Puls II wrote: > Off topic (but I couldn't find any contact info on the site) > > Could someone please fix ? The left side of > the page is inaccessible at < 1024 x 768 (800 x 600 for example), which > makes the site u

Re: [whatwg] Built-in image sprite support in HTML5

On Fri, 2010-05-21 at 10:12 -0700, David Weitzman wrote: > There are various approaches to using image sprites with HTML and CSS, > but at the end of the day they are all essentially hacks. A solution > that would be simpler than any existing approach would be to introduce > new attributes for to

Re: [whatwg] WebSockets: what to do when there are too many open connections

On Wed, 2010-05-12 at 11:01 -0700, Ojan Vafai wrote: > On Wed, May 12, 2010 at 4:31 AM, Simon Pieters > wrote: > > establishing a WebSocket connection: > > [[ > Note: There is no limit to the number of established WebSocket > connections a user agent can h

Re: [whatwg] Need document.available_fonts() call

On Wed, 2010-05-12 at 09:30 +0300, timeless wrote: > On Wed, May 12, 2010 at 5:37 AM, JustFillBug wrote: > > How about cloud computing? Gimp or CorelDraw like applications. There > > are already bitmap and vector editors in html5 using javascript. A user > > should be allowed to make use of the

  1   2   >