Opened 18 years ago
Closed 17 years ago
#249 closed New Feature (duplicate)
Normalize the order of tags' attributes
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | SF | Cc: |
Description
Open up an instance of the editor in Firefox and switch to SOURCE view.
Paste the following into the source window (overwriting anything in there):
<img id="resort_main_image" height="200" alt="" width="260" border="1" name="resort_main_image" src="full_10.jpg" />
Click OK to close the source window.
Open the SOURCE view again. Notice it has rearranged the ID and ALT attributes within the tag.
Click OK to close the source window, and then open it again.
The IMG tag is changed again, with the attributes in a different order. Rinse, repeat. It's always a different order.
This is causing us trouble because we are unable to compare submitted text against the database to check if it has been changed or not. There's no way to perform a "diff" on the page, as it will always be different in Firefox if it includes an image tag.
IE reorders it once, but then sticks with the ordering.
Moved from SF:
http://sourceforge.net/tracker/index.php?func=detail&aid=1430330&group_id=75348&atid=543656
Change History (7)
comment:1 Changed 18 years ago by
comment:2 Changed 18 years ago by
Reporter: | changed from Frederico Caldeira Knabben to jebsilver@… |
---|
comment:5 Changed 17 years ago by
Hello
Any plans on implementing this feature?
I use FCK inside a CMS. Changing a single word in a 100kb html document produces too many unrelated changes. The diff produced is many kbs instead of a couple of bytes.
thanks a lot. FCK rocks! :) Ioannis
comment:6 Changed 17 years ago by
Milestone: | → FCKeditor 2.7 |
---|
This feature would certainly bring some performance impact, therefore it should be configurable.
comment:7 Changed 17 years ago by
Milestone: | FCKeditor 2.7 |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
This one is now part of #1810.
There is no impact in the rendering with the current behavior (controlled by the browser, not the editor). We could think about a new feature in the editor that orders tags attributes alphabetically, for example.
Moved from SF.