If you have html and style sheet constructed information.
It super easy to detect, transform and replace

Example
/ style="text-align: left; width: 100%; background-color: rgb(255, 255, 255);" cellspacing="0" cellpadding="1" border="0" /
Would drive a Id name like this.

Tstalwhbcwp1b0

Now this would stop me for having the need to open 2 browser, 2 editor and transpose sort organize and Id, look up id, suggest to replace, and import into css file or use existing. I have perl program that can do this if need an example.

Origin html element are first charter driven, Table = T, Tr = t, Td = X, this would compress the html file, speed up the process and allow for table distinguishment.

Dreamweaver required me to enter my email and password. Since this was not a web page, I could not use the "Keeper" plug-in to fill in my password. I opened Keeper program and copied my Adobe password.

I tried to paste the password into the window you where Dreamweaver was requesting the password and it would not allow pasting of the password.

My passwords are 20 character unrecognizable passwords that are a pain in the neck to type in. I got it wrong several times until I pasted into Word and made the font bigger to get the right symbols and characters. (Ok, I guess I am getting older.)

It would be great if it could be pasted in. (It would even be better if Dreamweaver didn't lose the understanding that my mac mini was still the same mac mini and requiring me to log out of this mac mini so I can enable this new device - my same mac mini.)

I have used dreamweaver a long time and while i love some new features, there seems to be a lot more going on and loading, etc. in the background whenever i am running adobe products. Im running a beast machine and dreamweaver still bogs down when im trying to make time on simple projects anymore. If you are going to take a good solid program and overburden it at least give us the option to turn off features we dont need. i never thought that i would actually consider using another editor until now. And that is a huge statement. thank you

This request is to integrate the freely available W3C validator for CSS, expanding from the existing DW integration of W3C’s HTML validator.

The W3C validator that is integrated with DW for HTML (and XML) provides a valuable resource. The DW engineers who integrated it years ago were obviously being humble and realistic in recognizing that W3C would be able to provide for a perpetually more current and precise resource than DW linting, ultimately for the benefit of users and for user contentment. That was an archaic era before CSS files were commonly created separately from HTML. The difficult integration was done long ago, and now there is the relatively easy task of adding the CSS validator.

Since then, beginning years ago, W3C has also provided an API for the free integration of CSS validation into coding software. It is available at https://jigsaw.w3.org/css-validator/DOWNLOAD.html

Aligned with how DW is associated with Brackets and numerous third-party freeware utilities (and how Microsoft created its empire off of an IBM code), we users are willing to pay for the lawful licensing of a valuable utility, regardless of who had done the programming of any feature, as long as it is cleanly integrated, which was indeed well done with the HTML validator. Continuing with that analogy to DOS, there have been many predictions of its gradual decline, but by putting resources into DW to make it a leading editor again, Adobe can capture the perpetually expanding market of Web design.

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.

Thank you!