Re: CfC: publish Widgets PC as a Proposed Edited Recommendation; deadline August 28
On Tue, Aug 21, 2012 at 3:20 PM, Arthur Barstow art.bars...@nokia.comwrote: Please send all comments regarding this CfC to the public-webapps@w3.orgmail list by August 28 and note silence will be considered as agreement with the proposal. If you support this CfC, a positive response is preferred and encouraged. Editorial comment, Proposed Edited Recommendation references [DOMCore] in text, but Normative References section points to [DOM3Core] which is not used in text. -- With best regards, Pavel Zubkou. Mobile: +375293851118 Skype: pavel.zubkou
Re: Proposal for Cascading Attribute Sheets - like CSS, but for attributes!
On Aug 27, 2012, at 2:07 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
I have mixed feelings about this proposal overall, but I think it's a little
weird to use CSS property syntax instead of markup-like attribute syntax to
set attributes. I think this makes the syntax confusingly similar to CSS
even though proposed behavior is quite different. Something like this might
make more sense:
img.placeholder {
src=/images/1x1.gif
alt=
}
In other words, make attribute setting look like attribute syntax.
This is similar to the discussions about monocle-mustache in JS. I
prefer being able to simple re-use the existing CSS parser, but I'm
not completely wedded to it. I'd need some strong opinions from more
relevant parties to switch over, though.
I doubt we would be able to actually reuse the CSS parser, at least at the code
level, at least for WebKit. To give some examples of issues that arise:
- The CSS parser has specific knowledge of all the CSS properties we recognize
and their value syntax.
- It has no provision for catchall recognition of all other property names with
a quoted string value.
- There are some CSS properties that have the same name as meaningful HTML
attributes.
And finally, I'm skeptical whether the convenience here is worth adding a
whole new language to the Web Platform technology stack. It is literally
just convenience / syntactic sugar. I'm not sure that rises to the high bar
needed to add an additional language to the Web Platform.
Yeah, this is the major hurdle for this. My hope is that, by reusing
the CSS parser and restricting all the expensive parts of CSS
(dynamicness, remembering where a value came from, etc.), I can pull
the bar down low enough for this to make it.
I think your assumption is that it's possible to reuse the CSS parser is
incorrect, at least for strong values of reuse.
Regards,
Maciej
Re: Push API draft update
On Tue, 28 Aug 2012 02:00:11 +0300, SULLIVAN, BRYAN L bs3...@att.com wrote: Hi Art, Can you update the Webapps Publication Status page to add Eduardo as co-editor of the Push API draft? Done - you should be able to do it yourselves actually, using your normal W3C login credentials. We are looking forward to feedback on this update, with the goal of getting to FPWD by TPAC if possible. OK, noted. cheers Chaals Thanks, Bryan Sullivan + From: EDUARDO FULLEA CARRERA e...@tid.es Date: Wed, 22 Aug 2012 07:48:49 +0200 To: public-webapps (public-webapps@w3.org) public-webapps@w3.org Cc: bs3...@att.com bs3...@att.com Message-id: 492d97b30609c54fa9ff98b847ea5682b975989...@exclu2k7.hi.inet Hi all, Bryan Sullivan and myself have been working together on updating the Push API draft based upon feedback received and the work being driven by Mozilla and Telefonica to build a Push solution for Firefox OS (B2G). You can find it at: http://dvcs.w3.org/hg/push/raw-file/default/index.html This update does not intend to address yet each and every comment received, as some may deserve further discussions, but we think is a good step forward. We are looking forward to receiving your feedback. Thanks and regards, Eduardo Fullea Telefonica Digital Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- Chaals - standards declaimer
