Re: [whatwg] Web development
From: gbs...@msn.com To: wha...@whatwg.org Subject: Web development Date: Thu, 10 Oct 2013 12:04:28 +0100 Why is everything else around us developing so fast, but the web is so slow to adopt anything? It takes years just to add even the simplest improvements, or updates! I would like to see improvements to selectors. The way elements are selected on a page is hard work! Why can't a child select a parent in hover or any other target? HTML5 is a great advance, but in this case we still have to rely on jscript for most things!
Re: [whatwg] Web development
On Thu, Oct 10, 2013 at 7:12 AM, Mark Roberts gbs...@msn.com wrote: From: gbs...@msn.com To: wha...@whatwg.org Subject: Web development Date: Thu, 10 Oct 2013 12:04:28 +0100 Why is everything else around us developing so fast, but the web is so slow to adopt anything? It takes years just to add even the simplest improvements, or updates! I would like to see improvements to selectors. The way elements are selected on a page is hard work! Why can't a child select a parent in hover or any other target? HTML5 is a great advance, but in this case we still have to rely on jscript for most things! It's been proposed multiple times, but I don't think people came up with comfortable and understandable syntax. I've always solved this problem by rethinking how my DOM is laid out, though. What case do you have where an element changes on the state of its child? -- Jasper
Re: [whatwg] Web development
I have a case where an element serves as a tabulator of the states of its child elements which vary each time a new website is traversed or when a saved profile is loaded. It seems to me like the canvas element and its hit regions remedy this. Sent by the hope boat. On Oct 10, 2013, at 8:58 AM, Jasper St. Pierre jstpie...@mecheye.net wrote: On Thu, Oct 10, 2013 at 7:12 AM, Mark Roberts gbs...@msn.com wrote: From: gbs...@msn.com To: wha...@whatwg.org Subject: Web development Date: Thu, 10 Oct 2013 12:04:28 +0100 Why is everything else around us developing so fast, but the web is so slow to adopt anything? It takes years just to add even the simplest improvements, or updates! I would like to see improvements to selectors. The way elements are selected on a page is hard work! Why can't a child select a parent in hover or any other target? HTML5 is a great advance, but in this case we still have to rely on jscript for most things! It's been proposed multiple times, but I don't think people came up with comfortable and understandable syntax. I've always solved this problem by rethinking how my DOM is laid out, though. What case do you have where an element changes on the state of its child? -- Jasper
Re: [whatwg] Web development
On Thu, 10 Oct 2013, Mark Roberts wrote: Why is everything else around us developing so fast, but the web is so slow to adopt anything? Because to get something adopted in a browser, you need to do the following (not always in this order): 1. Have someone design the feature. 2. Have someone write a specification for it. 3. Have some people write tests for it. 4. Have one browser implement it. 5. Have another browser implement it. 6. Have another browser implement it. 7. Have another browser implement it. 8. Have people document it. This is in contrast to everything else, which just needs: 1. Someone to implement it. I would like to see improvements to selectors. The way elements are selected on a page is hard work! Why can't a child select a parent in hover or any other target? HTML5 is a great advance, but in this case we still have to rely on jscript for most things! For selectors, I recommend posting to the www-st...@w3.org mailing list. HTH, -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Web development
On Oct 10, 2013, at 2:45 PM, Ian Hickson i...@hixie.ch wrote: Because to get something adopted in a browser, you need to do the following (not always in this order): 1. Have someone design the feature. I have done this. 2. Have someone write a specification for it. I have begun this. 3. Have some people write tests for it. 4. Have one browser implement it. I have via having writ some XUL code had Firefox implement its most important feature. 5. Have another browser implement it. An associate built a Java browser demo of the same. 6. Have another browser implement it. 7. Have another browser implement it. 8. Have people document it. Not a coder myself, I need funding to hire and coordinate a team to reach the finish line. This is in contrast to everything else, which just needs: 1. Someone to implement it. I would like to see improvements to selectors. The way elements are selected on a page is hard work! Why can't a child select a parent in hover or any other target? HTML5 is a great advance, but in this case we still have to rely on jscript for most things! For selectors, I recommend posting to the www-st...@w3.org mailing list. HTH, -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
