Re: [whatwg] Site-Wide Heading Element

2015-06-30 Thread Martin Janecke
On 30.06.15 03:18, Garrett Smith wrote: On 6/29/15, Barry Smith bearzt...@live.com wrote: From: Garrett Smith dhtmlkitc...@gmail.com Hey Garrett, My apologizes for not replying until now. When I posted my reply to the Site-Wide Heading Element thread, you were right and I should have

Re: [whatwg] HTML6 proposal for single-page apps without Javascript

2015-04-05 Thread Martin Janecke
On 02.04.15 22:05, Bobby Mozumder wrote: On Apr 2, 2015, at 12:11 PM, Martin Janecke whatwg@prlbr.com wrote: On 02.04.15 04:59, Bobby Mozumder wrote: I understood that the motivation for your proposal is a shorter loading time for content on webpages. Your proposal might be one way

Re: [whatwg] HTML6 proposal for single-page apps without Javascript

2015-04-02 Thread Martin Janecke
On 02.04.15 04:59, Bobby Mozumder wrote: The best experience should be on by default, and you need a built-in MVC framework in HTML for that to happen. That's something you take for granted, but other people don't. Apparently, people want to see the claim substantiated. I understood that

Re: [whatwg] HTML6 proposal for single-page apps without Javascript

2015-03-28 Thread Martin Janecke
Am .03.2015, 02:51 Uhr, schrieb Miles Fidelman mfidel...@meetinghouse.net: […] It seems like: - It's getting harder and harder to do simple things. Too many JavaScript frameworks and libraries. Too much complexity. Authoring should not require extensive programming skills. (Whatever

Re: [whatwg] Responsive image maps

2015-03-26 Thread Martin Janecke
Am .03.2015, 11:10 Uhr, schrieb Simon Pieters sim...@opera.com: On Thu, 26 Mar 2015 01:47:57 +0100, Martin Janecke whatwg@prlbr.com wrote: Am .03.2015, 16:08 Uhr, schrieb Simon Pieters sim...@opera.com: […] It seems to me that there are two use cases: 1. variable-size image map 2

Re: [whatwg] Responsive image maps | inline SVGs in general

2015-03-25 Thread Martin Janecke
: On Sun, 22 Mar 2015 15:06:40 +0100, Martin Janecke whatwg@prlbr.com wrote: I've done a few tests and provide links to them below the following discussion. ... Test 4: https://prlbr.de/2015/03/inline-svg-without-height.html Test 5: https://prlbr.de/2015/03/inline-svg-without-size.html

Re: [whatwg] Responsive image maps | inline SVGs in general

2015-03-25 Thread Martin Janecke
A workaround for the bug in IE9+ is to add a wrapper element that does the responsive sizing. Something along the lines of http://jsfiddle.net/vo1ofz0w/1/. That's very helpful in practice, thanks! It didn't work 100% correctly yet (it pushes the figcaption away when the window is bigger than

Re: [whatwg] Responsive image maps

2015-03-25 Thread Martin Janecke
Am .03.2015, 16:08 Uhr, schrieb Simon Pieters sim...@opera.com: […] It seems to me that there are two use cases: 1. variable-size image map 2. art direction image map (1) is more common than (2). Yes, you're right. If there is implementor interest, I think it makes sense to make map

Re: [whatwg] Responsive image maps

2015-03-22 Thread Martin Janecke
I've done a few tests and provide links to them below the following discussion. Am .03.2015, 20:30 Uhr, schrieb Tab Atkins Jr. jackalm...@gmail.com: SVG is highly accessible. Yes, SVG a elements are followed just like HTML a elements, and yes, screenreaders do read out desc elements when

Re: [whatwg] Responsive image maps

2015-03-20 Thread Martin Janecke
Am .03.2015, 13:10 Uhr, schrieb Simon Pieters sim...@opera.com: Please leave out syntax proposals for now. What I think is needed first to drive this forward is: * Use cases. Why do you need this? In general it's needed to allow geometric areas on an image to be associated with

Re: [whatwg] Responsive image maps

2015-03-18 Thread Martin Janecke
Am .03.2015, 12:38 Uhr, schrieb Andrea Rendine master.skywalker...@gmail.com: […] why can't map area coordinates be responsive? I know that percentages simply don't work as UAs either interpret them as pixel, or they aren't interpreted at all. But what about rescaling? I'd like to

Re: [whatwg] alternate ids for elements

2014-12-03 Thread Martin Janecke
Am .12.2014, 15:30 Uhr, schrieb Nils Dagsson Moskopp n...@dieweltistgarnichtso.net: Julian Reschke julian.resc...@gmx.de writes: On 2014-12-03 15:02, Jukka K. Korpela wrote: 2014-12-03, 15:49, Julian Reschke wrote: I have a use case where a certain location in a document can have two

Re: [whatwg] @aria-labelledby | Re: @generator-unable-to-provide-required-alt, figure with figcaption

2013-06-20 Thread Martin Janecke
Am 19.06.2013 um 20:53 schrieb Ian Hickson: [...] I've changed the spec to make figure applicable to your use case as well, and added more text to explain various use cases and whether they apply to figure. Let me know if the new text is still problematic for your use case. I agree that

Re: [whatwg] use cases for figure without figcaption?

2013-06-20 Thread Martin Janecke
Hi Steve, The fact that they are enclosed in the figure elements means that they are referenced somewhere, I believe. so if not referenced somewhere, they should not be in a figure? Probably they should not, as figures are typically referenced as a single unit from the main flow of the

Re: [whatwg] @aria-labelledby | Re: @generator-unable-to-provide-required-alt, figure with figcaption

2013-06-19 Thread Martin Janecke
Am 17.06.2013 um 22:58 schrieb Ian Hickson: On Mon, 17 Jun 2013, Martin Janecke wrote: Am 17.06.2013 um 11:35 schrieb Steve Faulkner: the restriction on figure/figcaption is only in the whawtg spec not the W3C HTML spec as it was not deemed a useful or practical restriction when reviewed

Re: [whatwg] @aria-labelledby | Re: @generator-unable-to-provide-required-alt, figure with figcaption

2013-06-17 Thread Martin Janecke
Am 17.06.2013 um 11:35 schrieb Steve Faulkner: Is there a chance that use of aria-labelledby is added to the spec (4.8.1.1.13 Guidance for markup generators, 4.8.1.1.14 Guidance for conformance checkers) as alternative to figure with figcaption or the title attribute? I'd like to suggest

[whatwg] @aria-labelledby | Re: @generator-unable-to-provide-required-alt, figure with figcaption

2013-06-16 Thread Martin Janecke
Am 07.06.2013 um 23:13 schrieb Ian Hickson: img src=... title=image If you have a caption from the user (as opposed to replacement text), then this is a perfectly valid option. It's as valid as the figure case, and means the same thing. [...] I don't know whether someones writes

Re: [whatwg] sic element, was: Re: Exposing spelling/grammar suggestions in contentEditable

2011-04-30 Thread Martin Janecke
31, 2010 at 3:17 PM, Martin Janecke whatwg@kaor.in wrote: Am 30.12.2010 um 22:49 schrieb Benjamin Hawkes-Lewis: [snip] 1. What problem(s) does indicating where mistakes have been reproduced solve? I understand the question in this context as a concrete formulation of questions

Re: [whatwg] sic element, was: Re: Exposing spelling/grammar suggestions in contentEditable

2010-12-31 Thread Martin Janecke
Am 30.12.2010 um 22:49 schrieb Benjamin Hawkes-Lewis: On Thu, Dec 30, 2010 at 8:55 PM, Martin Janecke whatwg@kaor.in wrote: I don't think mark is appropriate for what I meant. I as the publisher usually don't mean[1] to point a readers attention at spelling errors by someone I quote

Re: [whatwg] element img with HTTP POST method

2010-12-31 Thread Martin Janecke
Am 10.12.2010 um 18:06 schrieb Julian Reschke: If the URI length is a problem because of browsers, fix the browsers to extend the limits, instead of adding a completely new feature. That's a good idea. Can we define a minimum length in the spec that should/must be supported? As a point

[whatwg] sic element, was: Re: Exposing spelling/grammar suggestions in contentEditable

2010-12-30 Thread Martin Janecke
Am 30.12.2010 um 02:47 schrieb Ian Hickson: On Tue, 30 Nov 2010, Martin Janecke wrote: I support this idea and I'd certainly use it. For example, I'm currently copying an old rhyme book to hypertext and would love to mark historically correct (but now incorrect) spelling, spelling

Re: [whatwg] element img with HTTP POST method

2010-12-10 Thread Martin Janecke
Am 09.12.2010 um 20:04 schrieb Ashley Sheridan: [...] If images are called with POST data, then that would prevent them being cached, which can be done with GET as GET isn't meant to change any state on the server, meaning potentially a lot more traffic [...] As I understand

Re: [whatwg] element img with HTTP POST method

2010-12-10 Thread Martin Janecke
Am 09.12.2010 um 20:41 schrieb Philipp Serafin: [...] though this would also present serious security vulnerabilities, especially in forum pages. There are quite a number of older web forums that sanitize their HTML using black lists and would not strip new attributes like post-data. For

[whatwg] element img with HTTP POST method

2010-12-09 Thread Martin Janecke
Hi all, What is your opinion on enabling the HTTP POST method for the img element? The motivation behind this is that there are services which generate images automatically based on parameters given -- nowadays provided as query string in a GET request -- for inclusion in web pages. I've

Re: [whatwg] Tag Proposal: spelling

2010-11-30 Thread Martin Janecke
Am 29.11.2010 um 21:58 schrieb Charles Pritchard: Currently, there's no way for an author to markup spelling errors in text. A [spelling] tag would address that deficiency. This could be used for a number of reasons, from [sic]-style annotations, to conveying to the user that an area is

Re: [whatwg] Tag Proposal: spelling

2010-11-30 Thread Martin Janecke
Am 30.11.2010 um 10:46 schrieb Martin Janecke: Am 29.11.2010 um 21:58 schrieb Charles Pritchard: Currently, there's no way for an author to markup spelling errors in text. A [spelling] tag would address that deficiency. This could be used for a number of reasons, from [sic]-style

Re: [whatwg] Processing the zoom level - MS extensions to window.screen

2010-11-25 Thread Martin Janecke
Am 24.11.2010 um 23:59 schrieb Charles Pritchard: There is evidence that it will enhance usability for programmers who use it properly. Focus. -Charles Do you mean functionality rather than usability? As I understand this, an author of a web page has neither control of nor knowledge

Re: [whatwg] whatwg Digest, Vol 80, Issue 47 | previously: Processing the zoom level - MS extensions to window.screen

2010-11-25 Thread Martin Janecke
Am 25.11.2010 um 17:41 schrieb Charles Pritchard: (2) The browsers' build-in zoom function, which web page authors have no control or information about. They have information about it, in many browsers, and they receive events related to window.innerWidth and innerHeight. Well, an author

[whatwg] Consecutive hyphen-minus characters in comments/in ACE-strings of IDNs

2010-11-02 Thread Martin Janecke
. Making -- valid won't affect any previously valid or invalid HTML page in any negative way, will it? Regards, Martin Janecke

Re: [whatwg] Please consider adding a couple more datetime input types - type=year and type=month-day

2010-08-31 Thread Martin Janecke
Am 31.08.10 03:36, schrieb Ian Hickson: On Tue, 24 Aug 2010, Martin Janecke wrote: Future browser could offer a calendar tool to fill input fields that have a date semantic. While this would be appropriate, it would not be appropriate to offer a calendar tool for other integer data e.g

Re: [whatwg] time element feedback

2010-08-31 Thread Martin Janecke
Am 31.08.10 21:40, schrieb Aryeh Gregor: On Tue, Aug 31, 2010 at 5:25 AM, Martin Janeckewhatwg@kaor.in wrote: Besides,time2010/time 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] base64 entities

2010-08-26 Thread Martin Janecke
Am 26.08.10 01:41, schrieb Adam Barth: On Wed, Aug 25, 2010 at 1:55 PM, Ian Hicksoni...@hixie.ch wrote: On Wed, 25 Aug 2010, Adam Barth wrote: HTML should support Base64-encoded entities to make it easier for authors to include untrusted content in their documents without risking XSS. Seems

Re: [whatwg] Please consider adding a couple more datetime input types - type=year and type=month-day

2010-08-24 Thread Martin Janecke
Am 24.08.10 12:38, schrieb Henri Sivonen: On Aug 9, 2010, at 04:07, Tantek Çelik wrote: * it has the *semantic* of being a year, which is a special type of number (potentially more than four digits if you subscribe to Long Now[1] methodology, or fewer than four as Andy noted). Why is it