From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020611 BuildID: 2002061104 Selected the "Retail Original source formatting" pref in composer. Had a select define in my HTML <select> <option> ...</option> ...more options... </select> after I saved, this was converted to <select><option>...</option>...more options</select> Not only does this formatting suck, but it wasn't supposed to format it at all according to the pref. Reproducible: Always
WFM in build 2002062308 PC/Win98. If you create a new profile and try it there, does the problem persist?
Created a new profile and tried it. Still reformatted after I set the pref not to. Tried again after restarting moz. Same behavior. Note, I don't think it is reformatting the same way it would if the pref is set. If I select the reformat option, add a space somewhere and save, it formats the HTML fragment to <select> <option value="12">12</option> <option value="24">24</option> <option value="36">36</option> <option value="48">48</option> </select> When I select the no format option, add a space and save, it immediately converts the above to <select><option value="12">12</option><option value="24">24</option><option value="36">36</option><option value="48">48</option></select> It seems like the no format option is really more like unformat :)
Is the preference/checkbox set backwards? Does it reformat select/option tags if you don't have the pref/checkbox set? Could you get a newer version of mozilla and test that? Perhaps this issue was already fixed in the last few weeks?
Summary: Composer reformats HTML on save when not supposed t → save reformats HTML when not supposed to (select/option)
It reformats the text if the checkbox is checked AND when it is not checked. It was not fixed as of 07/07/02.
> Is the preference/checkbox set backwards? Does it reformat select/option tags > if you don't have the pref/checkbox set? There are two radio buttons, one for "Retain original source formatting" and one for "Reformat Source Code". Each formats the HTML, but in different ways. > Could you get a newer version of mozilla and test that? Perhaps this issue was > already fixed in the last few weeks? I will update the bug report as soon as the 1.1beta is released, which should be soon, as (according the roadmap) the freeze date is today.
-->DOM to Text Conversion
Assignee: syd → harishd
Component: Editor: Composer → DOM to Text Conversion
Verified with Mozilla 1.1beta. This time I just used the html for a blank screen. I saved with Reformat then saved with do not reformat. The second save should have been the same as the first. It was not.
Last action was 2002-07-23 with Mozilla 1.1beta. Is this bug reproducable with Mozilla 1.7 (or Nvu)?
Yes this is reproducable with Mozilla 1.7.2 (Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.2) Gecko/20040804) I always code using XHTML so for meta tags, for instance, you need to use /> to close the tag. Both Mozilla and Firefox remove the / and retain the >: this makes tha saved page invalid XHTML. This happens for either setting of the "Retain Original Source Formatting"/Reformat HTML Source" radio button.
Stephen: Reformat concerns whitespace and newlines in the saved html source. For saving as xhtml, you want bug 45628.
Sorry, you've missed my point: when I save a Validated XHTML Page Mozilla reformats the page so it no longer validates. If Mozilla decides to add a feature to reformat a page into XHTML that that's great and very useful: my problem still stands - when I save a page I expect it to still validate if it did previously. Why does Mozilla chage the tags? It's unnecessary to do so, and de-grades the page. I should have reported this ages ago as it's always been the case.
reading comment #11, someone should change this bug status to "new".
firstname.lastname@example.org: no, as akkana said, this bug is not about xhtml. it's very much about *whitespace*. i'm most certainly not going to confirm it based on that. email@example.com: i hope you've found a closer match. note that mozilla composer doesn't claim to support xml or xhtml, so your bug would be an enhancement.
(In reply to comment #13) > firstname.lastname@example.org: no, as akkana said, this bug is not about xhtml. > > it's very much about *whitespace*. i'm most certainly not going to confirm it > based on that. > > email@example.com: i hope you've found a closer match. note that mozilla > composer doesn't claim to support xml or xhtml, so your bug would be an enhancement. No it's a bug, look at it this way: You take a W3C Validated webpage and save it using Mozilla - the saved page no longer validates! How is this an enhancement? You want Mozilla to give an indentical, which it doesn't.
Although this bug was created with a comment describing the problem using Composer, the bug is not an editor bug. It is correctly targeted to DOM to text conversion. The browser will have this bug. Composer will have this bug. Mail has this bug (though I think they strip the doctype so it wouldn't be easy to get it to reproduce it there). This bug does describe a problem with a composer pref not being honored. It is also specific to <SELECT> and <OPTION>. The original bug description and subsequent followups make no mention of XHTML or /> issues.
Summary: save reformats HTML when not supposed to (select/option) → save reformats HTML when not supposed to (select/option) [retain original source formatting pref not honored]
(In reply to comment #15) > Although this bug was created with a comment describing the problem using > Composer, the bug is not an editor bug. It is correctly targeted to DOM to > text conversion. The browser will have this bug. [snip] With that in mind, is this related to bug #118248? It sounds like very much the same problem: whitespace is changed, and I have recently observed that "Save as Web Page, complete" in Firefox 1.0 Mac also removes XHTML '/'s just as described (for Composer) in comment #9 above. (That's XHTML served as "text/html", of course; XHTML served as "application/xhtml+xml" doesn't give the "Web Page, complete" option for some reason.) As I understand it, in comment #13 firstname.lastname@example.org claims that the whitespace issue is distinct from the "deleting '/'" issue. I don't know the underlying implementation, and the two problems may in fact be technically unrelated. But I agree with the subsequent comments which insist that if Mozilla deletes _anything_ from the document as typed, it is not "retain[ing] original source formatting", whether it's deleting whitespace, '/', or anything else. (I guess that the term "formatting" might technically apply only to whitespace, in which case email@example.com is right. But then what should one call it when Composer deletes actual typed content? It sounds like this could approach "dataloss", depending on just how many things get silently dropped this way and how important those '/'s are considered to be.)
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Assignee: harishd → dom-to-text
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: sujay
Assignee: dom-to-text → nobody
QA Contact: dom-to-text
You need to log in before you can comment on or make changes to this bug.