Fast serialization doesn't check whether the document can produce mozdirty attributes

RESOLVED INACTIVE

Status

()

Core
General
RESOLVED INACTIVE
6 years ago
4 days ago

People

(Reporter: jdm, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
The changes from bug 599983 weren't taken into account in the final patch in bug 744830. We should see whether we can optimize the serialization further by checking nsIEditor::OutputsMozDirty.

Comment 1

6 years ago
I don't understand what can be optimized and how.
Can we make editor track its state using some private data structures on elements instead of attributes?

Comment 3

6 years ago
(In reply to comment #2)
> Can we make editor track its state using some private data structures on
> elements instead of attributes?

Sure, but somebody needs to write that patch.  Also, it's not clear to me how that would work when you copy and paste...

Comment 4

4 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 4 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.