Forum Moderators: open
I will kick off with the following suggestions :-
1) Deprecate event attributes such as onclick.
These should be replaced by a general script attribute thus :- <a href="mypage.html" script="onclick:'a++; return doSomething()'; onchange:'alert(''oops'')'">
The only minor problem with this is the handling of embedded quotes.
In addition, specialist script attributes could be defined such as javascript3.1 so that events are only assigned if the browser can understand the code. Using multiple script attributes, different handlers could be attached to events for older/newer browsers.
2) Create a client-side include method.
The obvious method is :- <div src="myfile.htmf">This page requires a newer browser</div>
Within the backward-compatibility text, a link could be added to download a newer browser.
This would be trivial to implement but I would suggest the following :-
- the .htmf extension is adopted for html fragments.
- optional <head> and <body> tags.
- optional <style> tag before any other tags (or within <head> tag)
The style sheet and scripts should be inherited from the parent page but have no effect outside the <div>.
I am only a part-time/amateur webmaster so maybe these features exist in newer or draft versions of HTML, but I've not heard of them.
Kaled.
I think backwards compatibility is unnecessary. At this point how many computers can't use a modern browser?
I had a computer from 1993 that could only run netscape 4.08; how many of these are there still?
Web design is a mess because not all browsers render code the same, especially with css-p. This, and getting better possiblities with css (ability to snap divs together, ability to allow divs to contain fully, ability to position by percentage better, ability to have multiple backgrounds), are crucial.