Cursor scroll position

[conmann]

When i edit a html file which has external css and js files, the scroll position is always on top of the file when i switch between the files.

Example:

I need to edit code at line 500 in my html file, scroll position is around that line, so i can see the cursor and the code i want to edit. Now i switch to an external CSS file. When i now switch back to source code of the html file, the scroll position ia at the top of the file, not at line 500 where my cursor is. Now i have to scroll down again to that line 500 where i want to edit the code.

Problem is on my iMac with macOS Sierra 10.12.5 (16F73)

Dreamweaver CC 2017.1 9583 Build

I do not have the problem on my Windows machine with the same Dreamweaver version.

How can i fix this? I can not work fluently if i have to scroll to down everytime.

[BenPleysier]

Have you tried Quick Edit (Ctrl+E)? I think that the problem was solved in 2017.2. It may be an idea to update.

[conmann]

Yes i use Quick Edit, but for refactoring i prefer switching between files. With javascript files i can not use Quick Edit.

Where can i get Dreamweaver 2017.2? My Creative Cloud Client does not offer any update.

[BenPleysier]

Log out and log in again might help

[ALsp]

Another (better, in my opinion) option is to turn off the Enable Related Files feature in Dreamweaver preferences. Then you can work with your files in a more natural way. You probably never need to edit a JavaScript file anyway, and if you need to open a CSS file for editing, then you simply open it from the Files panel. It's safer than using Related Files, too, as that feature opens a virtual copy of the actual file and can sometimes cause saving issues.

[conmann]

Thank you for your help.

I find the related files feature very useful for most purposes i have. On my windows computer the scroll position in Dreamweaver behaves as it should, but not on my macOS computer. I hope Adobe will fix this problem in a future version of Dreamweaver.

[Jon Fritz · Accepted solution]

Make sure to report what you're seeing, or add your voice to an already submitted bug report here: Adobe Dreamweaver: Bugs