Annoying loading animation above preview window. Can't seem to get rid of.

[Pat481]

Hi all,

i'm seeing the following loading animation (blue/ grey squares) above my work area. Very distracting, no 'X' button or way to get rid of.

Thanks.

[pziecina]

Have you any code in your html that loads any external resources?

[Pat481]

Yep, just images. They are all visible in the preview window.

[pziecina]

Dw 2017 has problems when resources are not on the local drive in the defined sites root folder.

This causes performance issues, which the dev team is investigating the cause of.

[Pat481]

Wow, don't the majority of projects use images hosted externally, even when testing locally?

On restart it went away, but it happens fairly commonly. Now it's this odd ruler thing which i can't make heads or tails of, and doesn't seem to align to the boarders of my project... I have nothing that aligns completely left and ends just off centre to the right..

Anyway, thanks for your (very punctual) help!

[pziecina · Accepted solution]

The ruler and 'green' bar if that is what you are referring to is the 'visual media query' indicator. To turn this off, go to the 'common toolbar', (the vertical one, used to be called coders toolbar) and the icon looks like an icon containing 3 horizontal lines.

As for external images, etc. js files appear to work in general, but other resources can and often do cause problems, I have found that opening in code view does help, (though this may be my imagination and wishful thinking ).

[Pat481]

Thanks for your help Jon, pziecina, much appreciated.  localising some of the style sheet calls helped, hopefully Adobe is working on this quirk. Not an issue I face with any other editors.

Bit confused by how this question is marked as solved. The issue was that there was a bug in Dreamweaver where valid code caused the media query bar to not load. Although going to the effort of localising files (that you should not need to localise) does seem to solve the issue, the bug is still there? If thats the way this forum typically works then that's fine, just strikes me as a little odd to mark it as 'solved' when the issue remains.

[pziecina]

Yes, the forum marks the question as answered when the problem is known and the dev team know about it.

One item that may help with the speed issue that I did not point out was -

I went through the site set-up (definition) and disabled the pre-processor 'compile on save' feature for every site, as I found this also did increase speed in Dw.

Time consuming I know, and a number of us did ask for this to be disabled by default in the Beta. I have complained that by the time something gets to beta, it is normally to late for something to be changed. Lets hope that some other way for user feedback on features can be found, that allows for features to be changed in the future.

[Jon Fritz]

Yep, that's the Visual Media Query bar. Looks like you have a single media query set to max-width of 480 pixels in your css.

Do you have any external sources in your CSS, like @import rules or server-hosted images background-image:url(http...)?

If you do, it might be worth bringing those into your local site during development. In my experience DW has always had issues with external references, so I've always used local versions, then as a last step if need be, I do a quick find & replace to add the external path info right before publishing.

[Jon Fritz]

I see that every once in a while in the Visual Media Queries bar, usually it only lasts a few seconds.

It could mean that you have an error in your media queries that DW doesn't know how to parse through. You might benefit from running the validator here to catch any major structural issues:

The W3C CSS Validation Service

That icon is used elsewhere in the program and will typically pop up if you're having connection issues and try to use certain features.

It might also be worth making sure DW can peak its head out from behind the firewall and access everything it's supposed to.

[Pat481]

Thanks for your help Jon, i've posted an update which is awaiting moderation.

[Pat481]

it does validate. The issues seem to be with the app.