Closed Bug 47014 Opened 25 years ago Closed 25 years ago

Paste does not honor dtd

Categories

(Core :: DOM: Editor, defect, P1)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: mozeditor, Assigned: mozeditor)

References

Details

(Keywords: dataloss, html4, Whiteboard: [nsbeta3-][p:1][pdtp1][rtm NEED INFO])

This is a catchall bug for the problem of Paste not making an effort to contruct a legal document. I'm duping some other bugs to this one. See them for specific examples.
*** Bug 43823 has been marked as a duplicate of this bug. ***
*** Bug 46550 has been marked as a duplicate of this bug. ***
*** Bug 46824 has been marked as a duplicate of this bug. ***
milestone, b3 nomination
Status: NEW → ASSIGNED
Keywords: nsbeta3
Target Milestone: --- → M18
Adding correctness and adding nsbeta3+
Keywords: correctness
Whiteboard: nsbeta3+
Whiteboard: nsbeta3+ → {nsbeta3+}
Whiteboard: {nsbeta3+} → [nsbeta3+]
setting priority in status whiteboard
Priority: P3 → P1
Whiteboard: [nsbeta3+] → [nsbeta3+][p:1]
adding dependency
Depends on: 46554
How is this critical to RTM...what will happen to user?
PDT: this is a correctness issue in regards to standards compliance, if this is not fixed, then we would be allowing invalid HTML into the document.
Changing priority to P4. Perfection is not what we should be shooting for here. If there are individual cases that are very difficult to recover from, we could consider a higher priority.
Priority: P1 → P4
Whiteboard: [nsbeta3+][p:1] → [nsbeta3+][p:1][pdtp4]
there are numerous issues -- movin td, th, li, etc -- all elements that have required parents can and will be copied/moved incorrectly. you should reconsider this one.
Agree with beppe. If this is not fixed, Composer will produce corrupted HTML files. Since we're corrupting the user data, this is in essence a dataloss bug. (A corrupted HTML file is an unusable HTML file.) Marking dataloss. Michael, how do we request a PDT review of this decision--clear the [p:1][pdtp4] keyword?
Keywords: dataloss
talked with pdt team yesterday, they agreed to have joe work on this one, bumping back up to p1, and removed pdt priority
Priority: P4 → P1
Whiteboard: [nsbeta3+][p:1][pdtp4] → [nsbeta3+][p:1][pdtp1]
Would not hold PR3 for this...please specify areas that will be fixed to help bound the scope of work.
as discussed in the pdt meeting, joe is working on ensuring that highly used elements such as <li> grabs the parent. We are not trying to solve all scenarios, just the most common.
Depends on: 50742
Marking nsbeta3- per Jim Hamerly's last comment. Nominating for rtm.
Keywords: rtm
Whiteboard: [nsbeta3+][p:1][pdtp1] → [nsbeta3-][p:1][pdtp1]
Joe, please include the required information per the rtm checkin rules
Whiteboard: [nsbeta3-][p:1][pdtp1] → [nsbeta3-][p:1][pdtp1][rtm+ NEED INFO]
Target Milestone: M18 → M19
Keywords: html4, mozilla0.9
removing + per pdt sw rules
Whiteboard: [nsbeta3-][p:1][pdtp1][rtm+ NEED INFO] → [nsbeta3-][p:1][pdtp1][rtm NEED INFO]
fixed.
marking FIXED per jfrancis' last comment (assuming he just forgot to do so).
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified in 10/13 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.