Unusably slow editing and false errors with CSS Grid and custom properties
This is an interim feature request to restore basic usability of DW, supplementing other feature requests relevant to full functionality. Dreamweaver continues to consider various CSS declarations of CSS Grid and CSS variables as being erroneous, which causes crashes and extremely slow processing, even in code-only view without linting. If these features are too difficult to incorporate into full DW functionality, simply an interim resolution that skips over such declarations would restore the usability. The problems particularly pertain to some CSS Grid declarations and to CSS custom-properties (often referenced as CSS variables).
A specific isolation pertains to unusable slowness with the fr (fractional unit) sizing, apparently in combination of the processing for linting and node.js.
I realize that there have been other feature requests pertaining to CSS Grid and to CSS custom-properties. My specific requests pertain to the unusably slow speed--even in Code View--when there are many lengthy CSS files connected toa Web site. I am thus proposing simple interim solutions of having DW ignore these declarations, so that there is not a timeout event that must occur with every line of editing. The timeout events appear to occur in node.js. Another excellent solution, which would re-enable linting, is to add these issues to the editable list of CSS linting features. The updating of the CSS linting features should be done anyway, so the interim solution would also be permanently valuable, with only a few easy changes made once DW can fully process Grid and custom-properties.
If we can resolve these first two issues, that would be a major improvement. I realize that you can defend yourself with arguments about compatibility, but a third issue of the same category of problems pertains to the CSS multi-permutation paradigm, particularly with such elements as has, is, and any. I wouldn’t want the third category of elements to cause this suggestion to be placed in a low priority, so I am only mentioning it if it can be incorporated efficiently into resolutions of the first two issues.
Considering that there already are feature requests pertaining to these issues for live view, hints, and linting, I am narrowing my requests to the extremely slow speed that apparently results from node.js processing code that DW falsely interprets as being erroneous. Two years ago, I abandoned the important features of live coding and linting in Dreamweaver (which are obviously important for coding) simply because Dreamweaver has become unusably slow, but even with purely Code-only views, Dreamweaver is simply unusable in conjunction with complex CSS programming, such as with more than ten thousands line of CSS coding, or even more than a few declarations involving these problematic coding. When I must use Dreamweaver for obsolete issues, I type the characters of a single line in CSS or HTML, and then wait for as long as five minutes for that string of characters to appear. Using this example, Dreamweaver must make a few simple updates, but by doing so it can resume being a relevant and useful program. Otherwise, the endlessly expanding global base of a large portion of the world’s population, who at least partially program their own Web sites, will be lost as a market for what could otherwise return to being a prominent, profitable, and respected program for Web development.
I would welcome the opportunity to collaborate with you by phone and E-mail on these issues. You are welcome to call me 24 hours, such as during Indian business hours, with my being motivated by the significance of the issues.