Skip navigation
mdgiamo
mdgiamo Calculating status...
Currently Being Moderated

Issue: DW CS6 vs. CS5: [the] "COMMAND>Clean Up XHTML" feature corrupts (?) code format in CHROME -

Jul 28, 2012 7:20 PM

Tags: #dreamweaver #xhtml #dw_cs5 #cs_5 #cs_6 #clean_up #dw_cs6 #code_format_issues_in_chrome_browser #code_format_problems_when_viewing_source #view_source_html #no_line_breaks #line_breaks_appear_to_be_missing_in_chrome_view_source #dreamweaver_chrome #chrome_xhtml #dreamweaver_cs6_chrome #xhtml_conversion

Greetings, all: I am new to the forum, here…sorry if this first entry is a bit long...but I am confused, here!

 

I write to explain an issue between Dreamweaver CS6 (which appears to consistently create the problem); vs. DW CS5 (which somehow consistently fixes it).

 

NOTE: The Preferences settings on both installs of DW CS5/6 for "Validator / Doctype" are "Transitional 1.0" (set on the same iMac, running OSX 10.7.4 (Lion). I've seen lots of weird things occur over the years when creating Websites and dynamic streaming media, etc.,...but never have seen this exact type of thing before when [any] part of the HTML / XHTML code that wasn't inheritantly - or obviously - faulty from the start...).

 

PROBLEM:

1. In DW CS6, using the "COMMAND>Clean UP XHTML" operation - after an [otherwise] normal-seeming conversion from an HTML 4.0 file to become a Transitional 1.0 XHTML file (all of which - despite the issue at hand - are perfect looking in layout and are completely functional when live from the Internet. Most of these files include one [or more] external CSS and JS files; some incorporate Fireworks CS5/6-generated JS / pop-up menus, also... that could be a clue...but why DW CS5 fixes this code, that DW CS6 "breaks" - is strange, indeed...sort-of BACKWARD ENGINEERING).

 

2. This issue occurs only when viewing a DW CS6 "XHTML converted" page's code in the CHROME browser - through CHROME'S "View>Developer>View Source" menu option. (No other browsers will replicate this "scrunching" of the code...).

 

3. What I see is: all of the page code is "run together" ... the [normal] line formatting is gone...as if no line break tags, or carriage returns, are present in the code (though they are visible as tags and / or blank spaces etc.). Virtually unreadable; may even present the impression of a badly coded Webpage / site. Printouts of the code (from Chrome's screen) are the same, too: scrunched together - character after character - no line formatting. BUT - when working with the code / design elements - in either DW CS6/5 Code view - everything appears perfectly normal, including when in Design view.

 

4. I've run the "faulty-appearing" code - and the URI's themselves - for assistance through some WC3 validators: different ones offer different errors or warnings, etc....but when I try to modify the code to "fix" Chrome's code display format issue  - nothing actually matches up to fix (that I can see, at least...). I have compared printouts of both "corrupted" and "normal" versions of the same code....difficult because of the run-on "paragraph of characters." The validators produce error issues: things like, "empty document on line one" of the page code (but it's not empty, of course); or validators note a missing "<" symbol on "line one" - but this symbol is not missing at all.

 

To see an example of what I mean, here....go to this URI of a copy of [one of] my own personal site's homepages: using CHROME (only):  http://www.dilettantefilms.net/index-BAD.html

and then go to: View>Developer>View Source  - to see what I'm talking about here...

 

 

HOWEVER...

 

5. If I open the exact same file(s)  => in DW CS5 <=  and perform the exact same operation ("Command>Clean Up XHTML") - DW CS5 fixes some type of tag or case mismatch(es) - a dialog box "tells" me that much - but not exactly WHAT was changed / corrected / or whre in the document, either. Then, after I re-upload a [DW CS5] "fixed" document - and again view the source code in CHROME - all the code formatting is totally NORMAL.

 

6. DW CS5 also FIXES the [unknown] "code problems" that DW CS6 somehow "broke." Go figure.

 

7. I have Googled the world over, re: this issue ... and Adobe's site, too … but find nothing about it. Does anyone else out there have this issue? Seen or heard of it - something like it; can suggest a solution...? Is there perhaps a now deprecated tag (or some other more recent change in code or CSS 3 "best practices") I haven't learned about, yet? Something that DW CS6 is sensitive to - but DW CS5 is NOT?

 

******

 

THANK YOU in advance...!!!

 

Message was edited by: mgiamo

 

Message was edited by: mgiamo

 

Message was edited by: mgiamo

1407 Views   5 Replies   Latest reply: webpointz, Sep 6, 2012 11:13 AM
 
Replies
  • webpointz
    Currently Being Moderated
    1. webpointz,
    Sep 4, 2012 10:04 AM   in reply to mdgiamo
    Report

    When running the command "Clean up XHTML..." I get the following log confirmation:

     

    "XHTML syntax fixed. 2 tag(s) and/or attribute(s) changed from mixed or upper case to lower case"

     

    The TWO tags it supposedly fixes and changes to lower case are in fact doing the opposite and causing code violations.

     

    It changes <meta name="keywords" to <meta name="Keywords" and <meta name="description" to <meta name="Description"

     

    The above changes not only go against the message from Dreamweaver that it changed to "lowercase", but capitalizing the names renders the meta data incorrect.

     
    |
    Mark as:
  • MurraySummers
    Currently Being Moderated
    2. MurraySummers,
    Sep 4, 2012 1:46 PM   in reply to webpointz
    Report

    The browser used to view a page cannot change the code on the page.

     

    Tell us why you are using XHTML, please.

     

    I am not able to reproduce your symptoms in CS6. The index-BAD.html page has no mixed tags and passes W3 validation at this location -

     

    http://validator.w3.org

     
    |
    Mark as:
  • Carey Burgess
    Currently Being Moderated
    3. Carey Burgess,
    Sep 4, 2012 4:46 PM   in reply to mdgiamo
    Report

    I'm not if the issue you're running into has anything to do with the Clean Up XHTML command.

     

    Like Murray, though, I am curious why you are using any XHTML.

     

     

    Are you using a Mac?

     

    If so, then I suggest that you change the Line Break Type in the Dreamweaver preferences to "CR LF" or "LF" to help avoid the issue going forward.

    Note that this will *not* fix the issue with any files that already have all their code running together. To fix existing files including index-BAD.html), try Commands > Apply Source Formatting.

     

    Hope that helps, but please let us know if it does not or if you have any other questions.

     
    |
    Mark as:
  • mdgiamo
    Currently Being Moderated
    4. mdgiamo,
    Sep 4, 2012 6:01 PM   in reply to MurraySummers
    Report

    Thanks for the advice on the "line return switch," everyone....and for the pin-point weirdness of Command>Clean Up XHTML. And also for someone pointing out the case-type mismatches...which is therefor truly a bug when DW6 changes the meta tag(s) in this way. DW5 seems to fix it, right?, when running the same command on the same Webpage. I note again: I am again using Macintosh computers almost exclusively these days. Also, I spoke w/Adobe/Dreamweeaver tech support staff last week. They seemed to be aware of [this problem] I'd experienced. They suggested a future patch or update will address it.

     

    FYI: Many Webpages I've made over the years started out with earlier versions of HTML (e.g. HTML 4.0). As time progressed (and much later my involvement w/coding) I rewrote - or converted - them in many cases - into XHTML Transitional 1.0 - which seemed to be the trend anyway; safer - less problemmatic as the W3C standards have changed. There is still a lot of XHTML Strict/Transitional out there on other folks Websites from what I see.

     

    What DO you recommend I be coding in - HTML 5?

     

    I did not do much new Web development for a few years...started again in 2010. I saw right away things had changed a lot. Obviated tags, etc. The gradual unveiling of HTML 5, etc.

     

    Everything I have read - even recently - states in one way or another that, while people are using HTML 5, it's "still in devlopment" and [not necessarily] considered the only - or "best" - code methodoloy to be used by the masses, yet. I still don't have a "definitive book" or guide to follow to begin to use it *specifically* from the start (though I've been to the W3C sites for occasional searches /info /research on "where it is" (by recommendation opf W3C) in "stability and use by other Web developers. I do still use or convert to XHTML Tranisitonal 1.0.  I use CSS 3 as much as possible - and have been the CSS use for years (still am); plus I employ JS: and my pages seem to work fine. I'm always looking for ways to improve them /the coding /my skill set(s). I learn more all the time just by looking at - and reverse enginering - other's more sophisticated code (open source is  a great thing).

     

    Am I missing something here, in "best HTML use practices.? I am technically behind the times? Advice would be most appreciated. Thanks!

     

    Message was edited by: mgiamo

     
    |
    Mark as:
  • webpointz
    Currently Being Moderated
    5. webpointz,
    Sep 6, 2012 11:13 AM   in reply to MurraySummers
    Report

    Maybe I'm in the wrong thread, but it makes no difference WHY i'm using XHTML...that's what my client's code is.

     

    Look, here's the issue.  When you are in DREAMWEAVER and you run the "Clean up XHTML..." command, it NEVER does what it SAYS it does.

     

    "If the document is in XHTML, select Commands > Clean Up XHTML.

    For an XHTML document, the Clean Up XHTML command fixes XHTML syntax errors, sets the case of tag attributes to lowercase, and adds or reports the missing required attributes for a tag in addition to performing the HTML cleanup operations."

    The above text is directly from DREAMWEAVER HELP.  Note the bolded text...this command is NOT putting "<Meta name="description"..." tags to lowercase...it's changing it from Lower Case to "Camel Case", capitalizing the meta NAME word.

    That's all I was trying to get across...

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points