- From: Glen <glen.84@gmail.com>
- Date: Sat, 03 Apr 2010 22:08:38 +0200
- To: François REMY <fremycompany_pub@yahoo.fr>
- CC: Brad Kemper <brad.kemper@gmail.com>, www-style@w3.org
- Message-ID: <4BB7A046.4090704@gmail.com>
I see. Well, I don't think it's a huge optimization that should prevent single-line comments from being implemented. UAs can simply be changed to collapse spaces/tabs only, right? On 2010/04/03 21:29, François REMY wrote: > No, it seems Brad is speaking here about two specific problems : > a { > property: //value; > } > should not be parsed otherly than { "property": "//value"; } because > '/' is an accepted char for the property values and is actually used > in some of the latest specs. > So, we should accept // only after a break ({, ;) and there's a > problem here > because some UA's are collapsing every space char (including line feeds) > to a single space char. > The problem would then become very visible : > a { > // non-ok : value; > ok: value; > } > <== UA Optimisation (discarding space chars after the first) ==> > a { // non-ok : value; ok: value; } > So UA's with such optimisation would not be able to apply a // comment. > Or at least, they would need to remove the optimisation. > > *From:* Glen <mailto:glen.84@gmail.com> > *Sent:* Saturday, April 03, 2010 9:16 PM > *To:* Brad Kemper <mailto:brad.kemper@gmail.com> > *Cc:* François REMY <mailto:fremycompany_pub@yahoo.fr> ; > www-style@w3.org <mailto:www-style@w3.org> > *Subject:* Re: Single-line comments > > On 2010/04/03 20:46, Brad Kemper wrote: >> I think as long as it was outside of the rule block and before the >> line feed character, it would just get thrown away, and the practical >> effect would often be the same as a comment. But if the white space >> (including line feeds) was ever collapsed into a single space (as >> some existing editors or optimizers might do), then it would >> interfere with the next selector. >> >> Anyway, the WG discussed the proposal on 2010-03-24, and it is in the >> minutes. The issue was closed. > > I didn't know it was discussed in the meeting, no one even replied to > my initial message to the list. RESOLVED with a question mark after a > short discussion -- interesting. > > The biggest point against it seems to be compatibility with older > browsers, which I addressed in my previous message. > >> On Apr 3, 2010, at 10:59 AM, François REMY wrote: >> >>> No theorical objection. They are practical objections though. How >>> will it work >>> when you use // comments with 'old' browsers ? It will not work. So >>> you can't >>> use it in a safe way. >>> >>> *From:* Glen <mailto:glen.84@gmail.com> >>> *Sent:* Saturday, April 03, 2010 7:26 PM >>> *To:* www-style@w3.org <mailto:www-style@w3.org> >>> *Subject:* Re: Single-line comments >>> >>> No replies? Does that mean no objections? :-) >>> >>> On 2010/03/19 21:08, Glen wrote: >>>> Hi, >>>> >>>> Has there ever been any discussion regarding the addition of >>>> single-line comments? //color: red; >>>> >>>> It's a lot faster to type when you just want to toggle a single >>>> declaration. It's also obviously useful for permanent comments >>>> where multiple lines are not required. >>>> >>>> Glen. >>
Received on Saturday, 3 April 2010 20:09:27 UTC