- From: Michael Norton <norto@me.com>
- Date: Thu, 10 Oct 2013 09:34:38 -0400
- To: "Jasper St. Pierre" <jstpierre@mecheye.net>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Mark Roberts <gbstar@msn.com>
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" <jstpierre@mecheye.net> wrote: > On Thu, Oct 10, 2013 at 7:12 AM, Mark Roberts <gbstar@msn.com> wrote: > >> >> >> From: gbstar@msn.com >> To: whatwg@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
Received on Thursday, 10 October 2013 13:37:53 UTC