[whatwg] [hidden] attribute should not allow overrides via css

2014-11-05 Thread Bruno Racineux
Those two lines from spec [1] are in conflict: Because this attribute is typically implemented using CSS, it's also possible to override it using CSS if something is marked hidden, it is hidden from all presentations The latter is not true as currently implemented. The former allows a css

Re: [whatwg] HTML spec incorrectly suggests that br can have its rendering changed with CSS

2014-01-28 Thread Bruno Racineux
On 1/28/14 1:04 AM, Elliott Sprehn espr...@gmail.com wrote: Blink treats br (conceptually) like a subclass of Text, there's nothing to style because it's just a run of text with a forced break. I'd just like to note that 'inline' styling for br should be allowed. I have been using it for a

Re: [whatwg] 'hidden' as resources control

2014-01-26 Thread Bruno Racineux
On 1/26/14 3:39 PM, Qebui Nehebkau qebui.nehebkau+wha...@gmail.com wrote: On Sat, Jan 25, 2014 at 4:13 AM, Bruno Racineux br...@hexanet.net wrote: What exactly do you find misguided, can you be more specific? Basically, - and I'm trying not to over-elaborate here, since my opinion isn't

Re: [whatwg] 'hidden' as resources control (Was: Simplified picture element draft)

2014-01-24 Thread Bruno Racineux
On 1/24/14 7:35 AM, David Newton da...@davidnewton.ca wrote: On Jan 23, 2014, at 10:52 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 1/23/14 9:13 PM, Bruno Racineux wrote: Could 'resource control' be an associated spec of the 'hidden' attribute? It bothers me, at first glance, to overload

Re: [whatwg] 'hidden' as resources control (Was: Simplified picture element draft)

2014-01-24 Thread Bruno Racineux
On 1/24/14 7:37 PM, Qebui Nehebkau qebui.nehebkau+wha...@gmail.com wrote: On Fri, Jan 24, 2014 at 9:09 PM, Bruno Racineux br...@hexanet.net wrote: The requirement for ATs with 'hidden' is to access the structure of hidden elements. Not the presentation aspect... I am having a hard time

Re: [whatwg] 'hidden' as resources control (Was: Simplified picture element draft)

2014-01-23 Thread Bruno Racineux
On 1/22/14 6:07 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 1/22/14 8:14 PM, Bruno Racineux wrote: Meanwhile, is there a way in which all vendors can prevent their pre-loaders from preloading (and loading at all for that matter) any img that has either: An html5 hidden attribute

Re: [whatwg] Simplified picture element draft

2014-01-22 Thread Bruno Racineux
On 1/22/14 3:54 PM, Adam Barth w...@adambarth.com wrote: The way we'd likely implement this feature in Blink is in couple stages. In the first stage, we'd implement the portions of the specification that don't involve media queries because we'll be able to provide developers a high-quality

Re: [whatwg] The src-N proposal

2013-11-20 Thread Bruno Racineux
On 11/20/13 6:09 PM, Kornel Lesiński kor...@geekhood.net wrote: With preload scanner limitation definitions in head is the best we could possibly do. I have proposed Media Query Variables intended to be used in style in head for responsive images. I've also wanted MQ variables to be usable

Re: [whatwg] The src-N proposal

2013-11-19 Thread Bruno Racineux
On 11/19/13 12:12 PM, Ian Hickson i...@hixie.ch wrote: On Tue, 19 Nov 2013, Markus Ernst wrote: I can't recall the reasons why Florian's proposal of combining picture and @srcset fell out of the discussion. To me it still looks like the most useable draft so far. I responsed to proposals

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-19 Thread Bruno Racineux
On 11/19/13 4:17 PM, Laurent Perez l.lauren...@gmail.com wrote: I'd like to propose the following pseudocode, building upon CSS4 range media queries. @media (3dppx resolution = 2dppx), (min-width: 320px) { .artdirection { background-image:url(high.png); background-position: center;

Re: [whatwg] The src-N proposal

2013-11-18 Thread Bruno Racineux
On 11/18/13 5:38 AM, Marcos Caceres w...@marcosc.com wrote: Agree. It would be ideal to try to find a way forward here with src-n. Mozilla is not really interested in restarting this whole effort again with imgset or new CSS-in-the-head proposals (though, of course, orthogonal improvements to

Re: [whatwg] The src-N proposal

2013-11-18 Thread Bruno Racineux
On 11/18/13 4:25 PM, Qebui Nehebkau qebui.neheb...@gmail.com wrote: Many people seem to find regexps difficult to understand, and the regexps involved would only get more difficult as the complexity of URL patterns increases. Forcing authors to use them sounds like a great way to guarantee

Re: [whatwg] The src-N proposal

2013-11-18 Thread Bruno Racineux
On 11/18/13 6:21 PM, Kornel Lesiński kor...@geekhood.net wrote: However, the most terse syntaxes are starting to look like Perl. It's not always the best idea to squeeze every byte out of a syntax. Even if none of existing proposals is perfect in terms of DRY, I think overall they're good

Re: [whatwg] The src-N proposal

2013-11-18 Thread Bruno Racineux
On 11/18/13 8:21 PM, Ilya Grigorik igrigo...@gmail.com wrote: On Mon, Nov 18, 2013 at 8:13 PM, Bruno Racineux br...@hexanet.net wrote: Because these (only 0.2% uzing gzip) stats do not look good at all in support of your theoretical argument: http://trends.builtwith.com/Server/GZIP-Module

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread Bruno Racineux
On 11/15/13 9:48 PM, matmarquis.com m...@matmarquis.com wrote: I¹d say the likelihood of a project not using a content image directory a step or two from root is roughly the same as the likelihood that I¹m hot-linking to images on someone else¹s website땧hich is to say ³very slim.² The ³real

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-16 Thread Bruno Racineux
On 11/16/13 3:24 PM, matmarquis.com m...@matmarquis.com wrote: I started and have been running the Responsive Images Community Group for nearly three years now.I helped build BostonGlobe.com and the original ³prototype² script for responsive images, I¹m a maintainer on the Picturefill project,

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-15 Thread Bruno Racineux
On 11/13/13 5:52 AM, John Mellor joh...@google.com wrote: style @media (max-width: 19.99em) { .artdirected { content: replaced image-set(128px; attr(srcs-smallicon)); } } @media (min-width: 20em) { .artdirected { content: replaced image-set(100% (30em) 50% (50em) 33%;

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-15 Thread Bruno Racineux
On 11/15/13 2:50 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: There is no compaction scheme that helps here. (Unless you're trying for one of the url-template ones, and we don't want to go there.) Why not? I'd like to hear the argument against what I am proposing. Either a regex or a

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-15 Thread Bruno Racineux
On 11/15/13 3:23 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: I don't understand. You don't repeat any sources, you specify them once. There's just a batch of sources per image. Can't make this more compact. What I mean is that with src-N you will have to repeat the paths AND the full

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-15 Thread Bruno Racineux
It does not require the preloader to have full css parser. It only has to parse @media and the new @imgset CSS subset language, using a similar syntax to @media. And I believe if offer an easy way to polyfill this. This isn't as terrible for polyfilling, since it's easier to spot things and

Re: [whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-12 Thread Bruno Racineux
On 11/12/13 12:11 AM, Adam Barth w...@adambarth.com wrote: On Tue, Nov 12, 2013 at 12:08 AM, Jukka K. Korpela jkorp...@cs.tut.fi wrote: 2013-11-12 9:58, Adam Barth wrote: Unfortunately, we can't add new tags to head. If the parser sees a tag it doesn't recognize in the head, it creates a

[whatwg] imgset responsive imgs proposition (Re: The src-N proposal)

2013-11-11 Thread Bruno Racineux
Here is a complementary approach to the src-N syntax, I'd like to present for discussion. The goal is: 1. Address all use cases in a similar way as src-N does without the 'N' part. 2. Cut the verbose to a 'strict' minimum with reusable OO definitions. 3. Provide a vocabulary that is easy to

Re: [whatwg] The src-N proposal

2013-11-08 Thread Bruno Racineux
On 11/8/13 10:46 AM, Rafael Rinaldi rafael.rina...@gmail.com wrote: It looks complex because it tries to solve something complex. I think there¹s no way to avoid verbosity to solve such thing. The only way to avoid verbosity on every img element would be to predefine a relationship between the

[whatwg] New social element (was: Various threads with feedback on HTML elements)

2013-10-22 Thread Bruno Racineux
On 10/15/13 1:00 PM, Ian Hickson i...@hixie.ch wrote: On Sat, 26 Jan 2013, Steve Faulkner wrote: Lists are appropriate for indicating nested tree structures. The use of lists to markup comments is a common mark up pattern used in blogging software such as wordpress. The code verbosity is

[whatwg] Behavior of anchor element when wrapping floated images

2013-10-14 Thread Bruno Racineux
I've ran into the following layout issue while using the accessibility audit extension on Chrome. https://github.com/GoogleChrome/accessibility-developer-tools/issues/64 In brief, there is an accessibility issue with floated images within an anchor element, which is present on the web on a

Re: [whatwg] Script preloading

2013-10-02 Thread Bruno Racineux
preloaders to fetch these scripts as soon as possible, in case they are needed. How common are media-specific scripts? On Mon, 15 Jul 2013, Bruno Racineux wrote: Wouldn't browsers be able to store pre-parsed/compiled' scripts in a separate byte code cache, with scripts promoted

Re: [whatwg] Script preloading: Browser Pre-compiled Scripts Cache?

2013-07-15 Thread Bruno Racineux
significantly, just like opcode does for php. And make CDN libraries even more useful and relevant that way. Or is this wildly nuts? In which case no need to answer. Bruno From: Andy Davies dajdav...@gmail.com Date: Saturday, July 13, 2013 5:55 AM To: Bruno Racineux br...@hexanet.net, WHATWG List

Re: [whatwg] Script preloading: Browser Pre-compiled Scripts Cache?

2013-07-15 Thread Bruno Racineux
On 7/15/13 6:12 AM, Yoav Weiss y...@yoav.ws wrote: On Mon, Jul 15, 2013 at 9:42 AM, Bruno Racineux br...@hexanet.net wrote: Taking about executing script as quickly as possible (threads from 1012 which I missed and tried to glanced through just get better educated about previous

Re: [whatwg] Script preloading: Browser Pre-compiled Scripts Cache?

2013-07-15 Thread Bruno Racineux
On 7/15/13 3:02 PM, Yoav Weiss y...@yoav.ws wrote: It goes beyond frameworks if based on pure 'access frequency'. For example, a site backend you use daily or you favorite web app would be also benefit. Including the G+, Twitter and Facebook site's scripts, Map APIs, Google News, or

Re: [whatwg] Script preloading

2013-07-14 Thread Bruno Racineux
On 7/13/13 5:55 AM, Andy Davies dajdav...@gmail.com wrote: On 12 July 2013 01:25, Bruno Racineux br...@hexanet.net wrote: On browser preloading: There seems to an inherent conflict between 'indiscriminate' Pre-parsers/ PreloadScanner and responsive design for mobile. Responsive designs

Re: [whatwg] Script preloading

2013-07-13 Thread Bruno Racineux
Nobody should be arguing about 'pet projects' or 'ignorance' here, it's really uncalled for. Characterizing strong counter arguments or strong views as 'attacks' is also unnecessary. May I remind you Alex that this thread's request for feedback started with two simple questions: Would something

Re: [whatwg] Script preloading

2013-07-12 Thread Bruno Racineux
On 7/11/13 6:00 AM, Jake Archibald jaffathec...@gmail.com wrote: link rel=subresourceŠ almost 50% of scripts Š sent without proper caching headers. If the browser is doing what it should do, it won't cache those This is not how link[rel=subresource] should work, the first request for the

Re: [whatwg] Script preloading

2013-07-11 Thread Bruno Racineux
On browser preloading: There seems to an inherent conflict between 'indiscriminate' Pre-parsers/ PreloadScanner and responsive design for mobile. Responsive designs mostly implies that everything needed for a full screen desktop is provided in markup to all devices. Isn't the

Re: [whatwg] Script preloading

2013-07-10 Thread Bruno Racineux
On 7/9/13 7:09 PM, Kyle Simpson get...@gmail.com wrote: I have been wrestling pretty hard with script loading issues lately. I'd say that having the browser manage script interdependency is probably a bad and cumbersome way to solve these issues. What do you mean by having the browser manage

Re: [whatwg] Script preloading

2013-07-10 Thread Bruno Racineux
On 7/10/13 4:20 AM, Jake Archibald jaffathec...@gmail.com wrote: On 10 July 2013 11:31, Bruno Racineux br...@hexanet.net wrote: Anyway, as per your previous email I think we mostly agree that solution #1 is not very practical (or infeasible per your word) Given the suggestions I made to #1

Re: [whatwg] Script preloading

2013-07-09 Thread Bruno Racineux
I just joined the list and glad this subject is brought up. I have been wrestling pretty hard with script loading issues lately. I'd say that having the browser manage script interdependency is probably a bad and cumbersome way to solve these issues. I'll try to explain, talk about the defer