[...snip...]
In the case of Netscape 4 compatibility, you should disable CSS in preferences and Composer will automatically use Netscape 4 attributes instead (using both is superfluous).
Thanks, this seems to work ...
When you create a new file Composer does not know where you are going to save it so it is forced to use absolute paths, but IIRC it will fix them up when you save it.
I would have expected this behaviour. Unfortunately, the composer sometimes saves an image as "file:///C:/[whatever]" instead of the relative path, even if the picture is in the same directory as the page being edited.
There's no such thing as an unused alt, if you read the HTML DTD you'll find that the alt attribute is required.
I agree on the principle, but practically, being forced to check the "don't use alternate text" button on nearly all pictures is quite annoying.
A feature I would like to see is a setting that allows the default to be reversed (no alt text by default) for picture that are below a user defined height/width treshold.
But finally, I do agree that the blank title could be improved on, this could be filed as a bug in Bugzilla (if it hasn't been filed already).
That would be good, but it's a very minor bug.
-----------------------
In facts, that was just a simple exemple, I could have used other examples, such as the unfortunate tendency it have for inserting a zillion useless blank lines in the code when you alternate from the WYSIWY(might)G and the source code, or other equally problematic behaviour.
What I'm searching is how to post-process the HTML code created by the composer transparently for the user. An event fired whenever the code has been changed, is about to be saved or published, an that would give me a pointer to check and modify it would be perfect.
Thanks for your time,
Eric.
