42 Errors, 91 warning(s)

What the people are doing 16 years later is using XHTML/HTML5 in a site that has a HTML 4.01 document type.
The legacy support you claim looks like it would break for some people if that keeps up.

That is one reason why people started to use BBcode 17 years ago, post would be portable to HTML changes and it would be harder for people to misuse HTML.

But If I listened to you. Then everything is all good and I'm dumb.

Ż\_(ツ)_/Ż

Comment on Re^4: Update the GUI (toolkit)

Replies are listed 'Best First'.
Re^5: Update the GUI (toolkit) by LanX (Saint) on Jul 21, 2016 at 05:09 UTC
Upvoted for the validator link! Still "Provide a migration concept which doesn't kill backwards compatibility and suggest a better design as default theme, please" Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^6: Update the GUI (toolkit) by $h4X4_\|=73}{ (Monk) on Jul 21, 2016 at 10:38 UTC
I suggest that PM ask for help in SOPW for solutions to the backwards compatibility issues that they face. Because if PM wants to keep its backwards compatibility issues a secret then there will be no work done to improve it. I am currently rewriting my own web framework/CMS, so I don't have programming restraints that prevent the code from moving on with life. The only thing that was holding it back was the theme design but that's fixed with new and better capability's. I would not do any work on this site till the owner agrees to use BBcode in it. Do you think they would agree to that?	[reply]
Re^7: Update the GUI (toolkit) by Your Mother (Archbishop) on Jul 23, 2016 at 21:33 UTC
BBCode would be dead last in preference to me; after plain HTML which it mimics badly without bringing much in the way of new/better affordance to the table. Some flavor of Markdown wedded with a good, semantic WYSIWYG input/editor is much closer to first.	[reply]