- if I am doing a manual virus scan of my machine, the minute the scan starts, dw becomes locked up and the GUI refuses to redraw and it might even say (not responding).
periodically for some unknown reason, (seems to be ANY disk accesses by some background app?) usually dw freezes during that time for about 5 minutes after the disk access is over. a few times it is shorter, but not usually.
- in all the dw cs5 built-in templates, charset for UTF-8 (should be upper case to meet w3c validation) is in as utf-8.
- <script></ doesn't close the tag with html5 pack. neither does anything with SVG or MathML, which are part of HTML5.
- the full set of modules for css3 and css2.1 are not supported in the HTML5 pack. I would like to do browser testing. I would also like to future-proof my investment! don't just do the minimums.
- the full set of HTML5 tags, attributes, input element types according to the w3c standard are not included in Insert, tag portion of the menu in the HTML5 pack.
- there needs to be a fixed refresh button for reinterpreting code/code+design/design view when changes have been made and something goes wrong like a redraw failure, or for when a problem has been fixed and you would like to see if dw sees any broken tags left.
- the feature in dw which you set in prefs that is supposed to "fixup documents with missing/mismatched tags" and such doesn't do that. it only makes lots of noises that it is doing so, but never does anything about it except throw up a dialog. I want it to fix the document like I told it to. broken feature. as it is, I have to make lots of guesses as to where those broken tags are, because dw doesn't highlight them either. I designed an algorithm I use in my bracematcher program at https://sourceforge.net/projects/bracematcher/ you might be interested in which would flag those orphaned open and close tags. I am sure you can do this yourself, it just requires knowledge of recursion and stacks and using == and != it's very simple. I was thinking might even be able to rewrite my program to work with tags, which would make it an even more interesting program. the lexer and string handling is the toughest part, and HTML is weird with strings on attributes. I really need to do this since dw isn't highlighting my tag problems. at least I can get a detailed report of the problems with my tags.