- From: Erik Bruchez <erik@bruchez.org>
- Date: Thu, 7 Feb 2013 10:19:36 -0800
- To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Cc: Public Forms <public-forms@w3.org>
Nick, I don't think target="new" is right. It was a placeholder for the topic to discuss. The original request doesn't mention "new". [1] I can see a double reason to use @target instead of @show: - it's compatible with HTML - it allows you to target a named tab/window ("browsing context" in HTML parlance [2]) In other words, @target is a superset of @show. Contrary to what the minutes say, @target doesn't seem to be deprecated in HTML5. At least I don't see any mention of that. So I would use @target. -Erik [1] http://lists.w3.org/Archives/Public/www-forms/2012Jul/0000.html [2] http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context-names On Thu, Feb 7, 2013 at 5:12 AM, Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com> wrote: > All, > > I have action https://www.w3.org/2005/06/tracker/xforms/actions/1909 to add > a target attribute on submission and load element supporting value 'new'. > But we already have a 'show' attribute with value 'new' on the load element. > > Shouldn't we add a 'show' attribute on submission then? > > Kind regards, > > Nick Van den Bleeken > R&D Manager > > Phone: +32 3 425 41 02 > Office fax: +32 3 821 01 71 > nick.van.den.bleeken@inventivegroup.com > www.inventivedesigners.com > > ________________________________ > > Inventive Designers' Email Disclaimer: > http://www.inventivedesigners.com/email-disclaimer
Received on Thursday, 7 February 2013 18:20:26 UTC