Thanks! I appreciate the suggestion.
As time goes on, I "relegate" messages, like the old IE messages, to legacy status which means they won't display unless legacy messages are enabled. In v17, message for IE versions below 8 should now be 'legacy' messages, but not for IE8 yet. In my opinion IE8 still has enough usage to have the IE8 messages still display by default. Part of the reason for this is that IE8 is the latest version of IE that can be installed on Windows XP.
I do like the option you suggest, but I do not think I would be able to keep up with it. The easier option of disabling messages for versions of IE previous to a specified version would be an easier option to add but the message "disable system" already in CSE HTML Validator
should work in the vast majority of cases and offer more precise control over what messages you want to see or not see.
If you later want to adjust the messages that are displayed after you have changed or disable them, you can in the Validator Engine Options
, Message Output->Message ID
Another option you might like is the "Enable override by message ID
" option in the Validator Engine Options
, Message Output
page. You can uncheck that option and then it will show all the messages again (including the ones you have disabled via message ID or exact text match), but the messages that have been disabled or changed will have a special "OVERRIDE" string prepended.
And of course the message you quoted has a "" in it, which means you can disable that entire group of messages by disabling flag 610. Here is a link to more details about flag 610:
https://www.htmlvalidator.com/v170/docs ... s_node.htm
So while more complicated (and more powerful), I think the "disable system" is the way to go. Unless I get more requests for what you suggest then I don't think I can justify the time adding such options. It's not that I think it's a bad idea or anything (it's not), it's just that what's there already can do the job and that there's not enough user requests for this.
Oh, and since browsers are becoming much more standards compliant and have frequent updates nowadays (thus always changing), I'd prefer not to add new options based on specific browsers if I can avoid it.