Re: [whatwg] Proposal: HTMLCanvasElement.printCallback API
On Mon, Jan 28, 2013 at 6:02 PM, Robert O'Callahan wrote: > On Mon, Jan 28, 2013 at 6:25 PM, Elliott Sprehn wrote: > >> 3) If we're advocating that developers "put a canvas on every page that >> covers the whole page" as the standard way to handle large document >> printing why not have a handler that gets given a canvas for every page >> automatically instead of requiring the developer to insert it themselves. >> > > Another use-case is when you have a document that's regular HTML and just > happens to contain one or more images that should be beautiful > when printed. > Why can't I do this for or or any number of other things then? All those things want to be beautiful when printed too. :) In that world I really think we want something closer to Element#printCallback. > 4) SVG is for vector graphics, not canvas. Why can't I replace an entire >> page with an instead of drawing to a canvas? :) >> > > SVG doesn't fit some use-cases very well, for example, when you generate > graphics from some underlying (large) data model. > Vector graphics is exactly what you want when the data model is really big though since it lets you prune out things you know can't be seen and stream the commands directly to hardware without rasterization as they're attempting to do with magic in this proposal. If SVG is broken for this use case we should fix that, it seems really sad to "give up" on SVG and bolt vector graphics onto . - E
Re: [whatwg] use of article to markup comments
List elements and sectioning elements both represent hierarchical relationships. They differ in how they emphasize that relationship: lists emphasize the hierarchy outside the content, while sectioning emphasizes the hierarchy within the content. If the question is specifically about how to mark up comments on a blog post or something, there's no reason you can't combine the two methods: Each comment is a self-contained , with relationships between comments represented by . One example: http://jsbin.com/edewoy/1 That example presumes you consider blog post comments (or replies to comments) as a section within the content that is being commented on (or replied to). You could also modify the markup to have two s (one for the blog post and one for the comments) packaged within a single parent , but the principle is the same. Note that the key here is that there is no restriction on combining lists and sectioning elements, and thereby no need to modify the semantics of or (as proposed in [2] in the root message). Gordon On Mon, Jan 28, 2013 at 12:13 PM, Steve Faulkner wrote: >> Brucel wrote: >> >> On Sat, 26 Jan 2013 10:56:10 -, 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 not >> > dissimilar to the use of article, less so even option end tags >> > are omitted. Besides comments are generated code not hand authored so >> > I don't see a problem with code verbosity >> >> [...] >> >> > >> >> (It makes some sense, I suppose, to think of comments as a "list", but >> >> *unordered*? If you're going to group them at all, wouldn't the order >> >> be important? Bruce Lawson ( >> >> http://lists.w3.org/Archives/Public/public-html/2013Jan/0111.html)'s >> >> observation that comments are "heavily dependent on context" would seem >> >> to support the idea that it *is* important, especially since some >> >> comments are responses to others.) >> > >> > agreed it would be better to use order lists. >> > >> >> Wordpress blogs, for example, have comments like >> >> "Bob Smith said at 9.55 on 31 Febtember: LOL" >> >> Thus, every comment has a link that a UA can use to jump from comment to >> comment. The order is implied via the timestamp. So what's wrong with >> >> >> Witty blogpost >> lorem ipsum >> >> >> 35 erudite and well-reasoned comments >> Bob Smith said at 9.55 on 31 Febtember: Can >> I use DRM in Polyglot documents? >> Hixie said at 9.57 on 1 June: What's your >> use case? >> ... >> >> >> >> >> In short, why should the spec suggest any specific method of marking up >> comments? > > Good question, in the case of recommended tomarkup comments > it seems like it's an element in search of a use case. > > For users who consume article semantics it appear to cause issues when > used for any piece of content ranging from a one sentence comment to > an article containing thousands of words or an interactive widget. > > > regards > SteveF -- Gordon P. Hemsley m...@gphemsley.org http://gphemsley.org/ • http://gphemsley.org/blog/
Re: [whatwg] Proposal: HTMLCanvasElement.printCallback API
On Mon, Jan 28, 2013 at 6:25 PM, Elliott Sprehn wrote: > 3) If we're advocating that developers "put a canvas on every page that > covers the whole page" as the standard way to handle large document > printing why not have a handler that gets given a canvas for every page > automatically instead of requiring the developer to insert it themselves. > Another use-case is when you have a document that's regular HTML and just happens to contain one or more images that should be beautiful when printed. 4) SVG is for vector graphics, not canvas. Why can't I replace an entire > page with an instead of drawing to a canvas? :) > SVG doesn't fit some use-cases very well, for example, when you generate graphics from some underlying (large) data model. Rob -- Jesus called them together and said, “You know that the rulers of the Gentiles lord it over them, and their high officials exercise authority over them. Not so with you. Instead, whoever wants to become great among you must be your servant, and whoever wants to be first must be your slave — just as the Son of Man did not come to be served, but to serve, and to give his life as a ransom for many.” [Matthew 20:25-28]
Re: [whatwg] [Notifications] Constructor should not have side effects
On 01/29/2013 12:15 AM, Elliott Sprehn wrote: The Notification constructor should not have side effects. This is generally considered bad design, and the rest of the platform doesn't have this either. Specifically new Notification() should not show the notification since it prevents reuse of the notification after calling close(), and is surprising behavior. (ex. new XMLHttpRequest doesn't fire the request, new HTMLDivElement() shouldn't append it to the document, ...) WebSocket, EventSource etc ctors do have "side effects". It feels natural to me that Notification is one time object. Once you've used it, you just create a new one if needed. Also, it is probably too late to change Notification API. -Olli
[whatwg] [Notifications] Constructor should not have side effects
The Notification constructor should not have side effects. This is generally considered bad design, and the rest of the platform doesn't have this either. Specifically new Notification() should not show the notification since it prevents reuse of the notification after calling close(), and is surprising behavior. (ex. new XMLHttpRequest doesn't fire the request, new HTMLDivElement() shouldn't append it to the document, ...) - E
Re: [whatwg] HTML5 web messaging - postMessage
Dear Travis, Glad to hear from you. Are you guys do volunteer job for that? or are you get paid for that? If you guys are volunteering there, I have no say about. If you guys do get paid, then please be professional and put things right at the first place. Bad standard wastes internet community's time, energy, and money too. with best regards Jack (Zhan, Hua Ping) +1-647-971-6390 On Mon, Jan 28, 2013 at 11:19 AM, Travis Leithead wrote: > Jack, > > With all due respect, this feedback is a little late. The spec in question is > now at candidate recommendation, and there are multiple interoperable > implementation in existence. While this is not to say that the spec cannot be > changed at this point, I would anticipate that many participants in the > working group (include myself) would be very hesitant to change their > implementations due to existing web compatibility. > > Having said that, I don't believe that the existing design of postMessage is > as bad is you make it sound :-) > > -Travis
Re: [whatwg] use of article to markup comments
> Brucel wrote: > > On Sat, 26 Jan 2013 10:56:10 -, 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 not > > dissimilar to the use of article, less so even option end tags > > are omitted. Besides comments are generated code not hand authored so > > I don't see a problem with code verbosity > > [...] > > > > >> (It makes some sense, I suppose, to think of comments as a "list", but > >> *unordered*? If you're going to group them at all, wouldn't the order > >> be important? Bruce Lawson ( > >> http://lists.w3.org/Archives/Public/public-html/2013Jan/0111.html)'s > >> observation that comments are "heavily dependent on context" would seem > >> to support the idea that it *is* important, especially since some > >> comments are responses to others.) > > > > agreed it would be better to use order lists. > > > > Wordpress blogs, for example, have comments like > > "Bob Smith said at 9.55 on 31 Febtember: LOL" > > Thus, every comment has a link that a UA can use to jump from comment to > comment. The order is implied via the timestamp. So what's wrong with > > > Witty blogpost > lorem ipsum > > > 35 erudite and well-reasoned comments > Bob Smith said at 9.55 on 31 Febtember: Can > I use DRM in Polyglot documents? > Hixie said at 9.57 on 1 June: What's your > use case? > ... > > > > > In short, why should the spec suggest any specific method of marking up > comments? Good question, in the case of recommended tomarkup comments it seems like it's an element in search of a use case. For users who consume article semantics it appear to cause issues when used for any piece of content ranging from a one sentence comment to an article containing thousands of words or an interactive widget. regards SteveF
