The editor in Dreamweaver 20.2 Build 15263 is so slow that I can regularly type ahead of the response on the screen, and I sometimes get a “not responding” message.
I am editing an HTML file that is 28KB, but has 20 images of approximately 25 KB each. In addition to the source code there is also the following: bootstrap-4.2.1.css file, custom.css, jquery.fancybox.min.css, nav.inc. footer.inc.
Other open applications include MS Word, Firefox, and Outlook.
All files reside on the my desktop PC, which is an Intel(R) Core(TM) i3-6300 CPU @ 3.80GHz, with 16.0 GB Installed RAM, running a 64-bit OS and Windows 10 Pro, Build 18362.959. No processor has more than a trivial amount of usage and no disk is much more than half used.

BTW, the Dreamweaver editor is slowest when backspacing.

I have noticed there has been a recent issue with Dreamweaver when typing it is either a lag in the input or either it does a slight freeze. I have checked my own computer to make sure and have enough RAM to run it and other things in the background.

Even have disabled prior applications to test it and still a lag in the interface when trying to code HTML templates and other markups. The only one that doesn't have an issue filetype wise is coding CSS stylesheets. I don't know if this was reported before, couldn't find it searching for the issue earlier but this showing to be an issue and major one now that I have noticed.

On macOS it is very easy to save an HTML file without the .html extension. DW isn't smart enough to correct this oversight.

If you create a new HTML by File > New then choose the first document type HTML and then finalise with Create you are placed into a new untitled HTML document.

When you attempt to save on macOS you will first see the text field for the file name with selection highlighting. The default filename and extension is highlighted. Immediately typing anything will overwrite both the file name and the extension. So you might type, "cool-site" hoping to save as cool-site.html.

However, the save dialog is passive and doesn't actively pick up the fact that you haven't added a file extension.

But the file should realise from the original template that it is an HTML file. The file is added to the project but because it has no file extension, DW then thinks it can't be edited.

Solution. Don't fully highlight the entire file name when the Save Panel is opened, instead highlight the base name and not the extension.

But also play nicely with the built in NSSavePanel, it knows how to hide file extensions properly.

I'm developing a drupal site, but actually I'm just trying to use DW2020 for rapid iterations, which I would normally use browser developer tools and my IDE(vscode). It's wonderful to see Dreamweaver back in the App lineup. (I'd love to see asp.net and other template based things suppported and yes I've seen the extensions)

To recreate my situation with a fresh copy of dreamweaver:
Choose open file, type https://test.resurgenceevents.org as the filename. Open it, and add this tag to the HEAD section of the html (without the space before last speechmark needed to post as comment):
<base href="https://test.resurgenceevents.org/ " />
The page loads in split or live view and is nearly unusable, as is the dom tree or anything really. Second(s) of delay to everything.

It's hilarious to try and navigate to the last stylesheet, I was hoping the double arrows at the end of the stylesheet top panel would bring up a modal dialog to easily navigate them by keyboard or filtering. I also thought they would appear in the css designer tab but maybe I was too impatient for it to load?

Dreamweaver 2020 on Windows 10 is extremely text unfriendly compared to DW MX. It is forever taking time off to think about the simplest edit and it moves from display to code ridiculously slowly. I have lots of memory - that isn't the problem. It repeatedly flashes "not responding" and does so when it's closing to. It feels like a good application has been ruined by over-elaboration. What is it doing with my memory? Other things - the Find and Replace function is much worse than previously and no longer integrated. I dislike the killing of anchors though I understand the ID issue. To be brief - you have ruined my straightfroward webwriting experience and jeopardises a big site at www.ricorso.net. Hope your very sorry, Mr Adobe. I'm pretty sick at you.

I am having a persistent problem with DW 2020 v. 20.2 15263 where pages will open (slowly!) and in split view or code view the code will not show up (see attached). I have tried this is safe boot and the issue persists, but not every page every time. I also note that when using some features of WebAssist's wizards, the screen will cycle and go into complete limbo for minutes at a time, although the connection to the database is immediate. I am NOT having this problem on my 2014 MacBook Pro, so I am assuming it is the graphics card and DW.

I am running a Late 2013 with 3.5ghz 6 core Xenon E5, 16GB memory AMD FirePro D500 3 GB . In general, page redraws are very slow.
Mac Mojave 10.14.6, my Macbook Pro is running Catalina.

The scenario is DW 2020 (on macOS 10.15.5) is editing web pages where the artwork is too big. So the image need to be down sized. Have set up Photoshop to be the Primary editor for JPG files.

When you select the image in Live view, properties window updates.
Can see the current size of the image.
Click the Photoshop icon
In Photoshop
Image Size change
Save again, adjusting the JPEG compression ratio
Back in DW

Properties doesn't update
DW is not picking up any change to the file status for the file it just went off to edit.
This should update the width and height properties if I have actually edited the file or give me some warning that I should pay attention to the discrepancy between the image and what is in the img properties.

If you are busy, you don't remember both width and height changes in Photoshop. So if you want to update the width and height you have to go back an look. If you are maintaining aspect ratio, you really only pay attention to one of these, not both.

.15263 on 10.15.6 (19G73)

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: EXCI386GPFLT
Exception Note: EXCCORPSENOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [80257]

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.apple.CoreGraphics 0x00007fff31c57b55 CGGlyphBitmapRelease + 9
1 com.apple.CoreGraphics 0x00007fff31c57d59 CGFontStrikeRelease + 60
2 com.apple.CoreGraphics 0x00007fff31c9889e CGFontCacheReset + 79
3 com.apple.HIToolbox 0x00007fff3044abb8 HIApplication::FrontUILost() + 52
4 com.apple.HIToolbox 0x00007fff30443f4a HIApplication::HandleActivated(OpaqueEventRef, unsigned char, OpaqueWindowPtr, unsigned char) + 502
5 com.apple.HIToolbox 0x00007fff3043e2be HIApplication::EventObserver(unsigned int, OpaqueEventRef, void) + 184
6 com.apple.HIToolbox 0x00007fff304050b9 NotifyEventLoopObservers + 153
7 com.apple.HIToolbox 0x00007fff3043dd55 AcquireEventFromQueue + 522
8 com.apple.HIToolbox 0x00007fff3042c72d ReceiveNextEventCommon + 416
9 com.apple.HIToolbox 0x00007fff3042c579 BlockUntilNextEventMatchingListInModeWithFilter + 64
10 com.apple.AppKit 0x00007fff2ea72039 DPSNextEvent + 883
11 com.apple.AppKit 0x00007fff2ea70880 -[NSApplication(NSEvent) nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
12 com.apple.AppKit 0x00007fff2ea6258e -[NSApplication run] + 658
13 com.adobe.exo.framework 0x0000000112991138 exo::app::OS_AppBase::RunEventLoop() + 56
14 com.adobe.dreamweaver-18.1 0x000000010df86d99 CRealApp::Run() + 953
15 com.adobe.dreamweaver-18.1 0x000000010df550b2 main + 674
16 libdyld.dylib 0x00007fff6b86ccc9 start + 1

I have created a template and created an editable region. The non-editable regions are the header, footer, etc. But whether it's existing pages based on this template or new pages created from this template, the non-editable regions are editable and not grayed out like they used to be.

What I've tried:

• Updated to most recent Dreamweaver




• Restarted Dreamweaver and the computer




• Created a new page and made sure the box is checked that links it to the template when it's updated




• applied it manually but after existing Dreamweaver reverts back to no greyed out areas

*restoring preferences

I have been told it is a bug