W3C home > Mailing lists > Public > public-html@w3.org > May 2015

Re: A New Element

From: Greg Babula <gbabula@gmail.com>
Date: Wed, 20 May 2015 11:09:04 -0400
Message-ID: <CAKqr0s2HtcVGVMeA986BagqQGvbxM83mp=a7aFKmzGQQSS2ptw@mail.gmail.com>
To: Martin Janecke <w3.org@prlbr.com>
Cc: "HTML WG (public-html@w3.org)" <public-html@w3.org>, Leo Wilson <LWilson@xlww.net>
Since some closing tags are optional in HTML5, would this idea work
specifically for tags that require closing?

Seems like a nice to have for quick debugging (especially in older
browsers).

However I don't see a significant amount of developers having a need for
something like this.



Thank you,


On Wed, May 20, 2015 at 10:12 AM, Martin Janecke <w3.org@prlbr.com> wrote:

> On 20.05.15 01:07, Leo Wilson wrote:
>
>> I think you should in you next recommendation you
>> should include a “</*>” element that would close all elements except
>> for head, body, and html elements.  This would help, …
>>
>
> Leo, in which situation would that help? Why would, say, <b>…</*> be
> better than <b>…</b>?
>
> Or do you mean that it would save authors time because they can quickly
> close open elements without checking what the open elements are? But if
> they don't check, how do they know they want to close these elements at
> that point?
>
>  … and would also
>> encourage proper syntax with the closing of elements, one thing that
>> HTML 5 doesn’t absolutely require to operate without errors.
>>
>
> I'm not sure I understand this. How would it encourage proper closing? I
> suspect that a new wildcard closing tag would rather encourage people to
> stop using the most proper, readable tag that uses the same name as the
> element's opening tag.
>
> An example may help to illustrate your idea. Can you please provide one?
>
> Thanks, Martin
>
>


-- 
*Greg Babula*
*User Interface Engineer*
http://GregBabula.info <http://gregbabula.info/>

*------*
*NOTICE: This communication (including any attachments) is covered by the
Electronic Communications Privacy Act (18 USC 2510 et seq) and is intended
to remain confidential.*
*------ *
Received on Wednesday, 20 May 2015 15:12:10 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:13 UTC