![]() ![]() I did myself that experiment you describing, discover differences in code. Grove ,must tell you, you nail it like old pro ……………. My fee for this consultation will be two bottles of scotch. So my first suggestion might work better for you. However, this would require modifying the code directly-and may require a bit of tweaking and experimentation-which may not be your preference. Much in line with Linda's suggestion (and my own on your previous post), you could instead opt to address this problem by adding a small CSS declaration to the existing style tag within the head of your HTML document, something like this: But that doesn't mean it's not good for some things-like design, or certain aspects of the development process. I wouldn't trust Fireworks as a resource for contemporary web development practices. That's why Internet Explorer is showing you blue borders, where Google Chrome is not. Each web browser has a tendency to interpret those instructions slightly differently. When creating web designs and converting them to code, you're creating instructions for a design rather than the design itself. The bad news: Web development is a constantly moving target. And once you've made this change, it should become the new default for all your Fireworks CS6 documents. (Or choose Generic HTML.) This seems to bring back the border="0" attributes. and then under the HTML Style dropdown menu, select "Generic XHTML" instead of Dreamweaver XHTML. Within Fireworks CS6, go to File > HTML Setup. The good news: If you're looking for an easy fix for this, I think I've got one for you. But then again, the use of slices, in general, is not a contemporary, standards-based method of web development-except, perhaps, in small doses. ![]() The use of style attributes on HTML tags (as in CS5) is deprecated in favor of using CSS rules. Believe it or not, the CS6 version is probably better, from a contemporary coding standpoint. See the difference? The CS5 version is riddled with border="0" attributes on every img tag. The second shows the HTML output from CS6. This first graphic below shows the HTML output from CS5. I used the default export options for both CS5 and CS6, then opened both HTML files in Firefox and used its View Source option. I tried this myself, using a simple Fireworks file containing just a single slice. Use Dreamweaver's code view, or use the View Source option that's available in most web browsers. When it comes to HTML output, the answer should be somewhere in the code. A good strategy would be to create a simple file in CS5, and then export it twice: first in CS5 and then again in CS6. You've already made progress in isolating the problem: It occurs in CS6 but not in CS5. This is document how it look in Fireworks: No big deal for me, just have to use CS5,…just try to help developers fix bags….if they care… ![]() You can just create only hot spot in empty document, and it happened too, just first description is better to see. I am old enough to still remember old good times, when people still care and if you call from English speaking country, you got help speaking English.Īnyway, problem is, if you create a new document, and create a small slice in the middle, then create a hot spot bigger then that slice, and preview it in MS explorer, you will see some blue borders, frames around slices. I just guessing, nobody give a s….t anymore, nowhere, and that seems to be a problem in all around us, that is why economy sucks and…. I discover a problem or bug in Fireworks CS6 while ago, posted in Fireworks forum - no answer…report it like a bug to adobe – no answer,….call to technical support,…after been on hold ,described all info, on hold again, I got answer: report it like a bug on adobe side and support forum ,when I told support person, that I did that already, he told me, nothing else he can do for me… ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |