Design View Bug

Report · Apr 16, 2018

Using the following code:

<html>

<head>

</head>

<body>

Dreamweaver Test

</body>

</html>

When I open a file with the contents the Split/Design View shows this:

When I copy and paste into a new tab it shows this:

The appearance of the text is incorrect when the former, and correct in the latter.

Reproducible: 100%
OS: Windows 7
DW: CC 18.1 Build 10155

Report · Apr 16, 2018

Can you verify your magnification setting is 100% in that document?

View > Design View Options > Magnification

Magnification is "per document" so subsequent copy/pastes from the original would not be zoomed in on.

Report · Apr 16, 2018

The magnification level for both documents is 100%.

When I save the second file (and close DreamWeaver) and then reopen the file, the font size changes.

Report · Apr 16, 2018

I can reproduce the same behavior here with your code.

Same OS and DW Build.

However, once I modify the code to match HTML5 specs, it stops enlarging the text when opening the file...

<!doctype html>

<head>

<title>Dreamweaver Test</title>

<style>

span {

font-size:12px;

font-family:verdana, geneva, sans-serif;

}

</style>

</head>

<body>

Dreamweaver Test

</body>

</html>

Report · May 15, 2018

I'm not understanding why Jon's post was marked as "CORRECT". He confirmed this is a bug as he was able to reproduce the issue.

Can someone provide a link to submit this to Adobe developers?

Thanks!

Report · May 15, 2018

It's also available in DW under Help > Submit Bug/Feature Request

Adobe Dreamweaver: Bugs

Report · May 15, 2018

Thank you Jon! Right in front if me it appears

Report · May 15, 2018

I think what was implied, but not directly stated is that the following code is invalid:

Dreamweaver Test

So, the question is really, "should Dreamweaver Design View render invalid code in the same manner a browser does?" More importantly, would it be beneficial to you if you used valid code? There is actually no reason to use font-face. The valid version of your code would be:

Dreamweaver Test

Report · May 15, 2018

The code is not mine. I am not in control of user submitted code.

Dreamweaver should be:

#1) Consistent

#2) Render the way a browser would render

The issue has been confirmed by what appears to be an Adobe MVP.

Report · May 15, 2018

Easy, dude. I'm just trying to help you. Jon is very astute, but that is not a requirement for Adobe MVPs. I agree that Design View should not care about rendering invalid code. The fact is that for twenty years, Design View has been a less-than-reasonable facsimile of what a browser displays. This is common knowledge among long-time Dreamweaver users (like me), and it is something Adobe has not tried to mitigate. Their resources are in Live View. So, I will let you on your own and apologize for trying to help you. You are free to use invalid code as often as you like.

Report · May 15, 2018

If you use invalid code (denoted by a red X under your document), you can expect rendering issues in Design View because it's not a browser. At best it's an approximation of what you'll see in some older browsers. Design View is a holdover from the old Macromedia days. My understanding was that Design View would eventually be phased out and replaced with Live View. So I doubt the engineers will be putting much effort into Design View bugs.

See screenshots below. The first with your invalid code.

The second shows the same code with obsolete font face tag closed.

Nancy O'Shea— Product User, Community Expert & Moderator

Design View Bug

1 Correct answer