[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-28 Thread registrierungs genervter
@TiddlyTweeter No, it is not my normal name :-) I agree with you and Arlen Beiler regarding the *p*s. It has three aspects: - *p*s are better than *br*s because *p* is semantic and *br* is not. *p* is also easier to parse. - but wrapping *div*s into *p*s results in invalid html

[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-26 Thread @TiddlyTweeter
Ciao registrierungs genervter I think Arlen's recent thread relates to this too?- https://groups.google.com/forum/#!topic/tiddlywiki/VBrRCeYka1I Best wishes Josiah On Sunday, 24 March 2019 21:43:45 UTC+1, registrierungs genervter wrote: > > When trying to parse the document structure of an

[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-26 Thread @TiddlyTweeter
Ciao registrierungs genervter (Is that your actual name :) Great post! Very illuminating & informative. Looks definitive. I deleted my last post as utterly naive on HTML 5 in-browser. The "spare" p's in TW look like clutter. But escape detection in 5 validation so live on? Is that the

[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-25 Thread registrierungs genervter
If i am not wrong a *div* was never allowed inside a *p* (because the content model of *p*s is phrasing content ). I tested it: HTML 2.0 Is a in a p allowed? Lets see. results in element "DIV" undefined. The div element

Re: [tw5] Re: [Bug] Misplaced closing p tags.

2019-03-25 Thread @TiddlyTweeter
It's an interesting issue! In both coding and semantics. To my mind it was odd that that HTML 4 rule was abandoned. Div went from king to ordinary vassal. Probably one of the most radical steps of 4 to 5 in terms of legacy? But maybe it was right. Perhaps for good reason, in the sense that

Re: [tw5] Re: [Bug] Misplaced closing p tags.

2019-03-25 Thread Jeremy Ruston
Hi Mario I’ve just been checking this out too. It seems that the problem is this construction: In other words, a paragraph containing an empty div. If I paste that fragment into the text input node of https://validator.w3.org/nu/#textarea in place

[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-25 Thread PMario
Hi, I had a closer look. There seems to be a problem with the validator in strict mode. If you open the TW source 2 lines above is the opening p-tag. BUT at the moment TW UI creates some unnecessary "invalid" p-tags. ... So the validator may be confused. ... --- Be aware! The

[tw5] Re: [Bug] Misplaced closing p tags.

2019-03-25 Thread PMario
Hi, You are right. the div and the p tag have to change places. I'll create a fix and a PR. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to