Closed Bug 14753 Opened 21 years ago Closed 20 years ago

Definition list, description, and term don't work

Categories

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

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sujay, Assigned: mozeditor)

Details

(Whiteboard: (fix in hand) [nsbeta2+])

using 9/23 build of apprunner

1) launch apprunner and editor
2) highlight some text
3) pull down from attribute menu description term or definition description

nothing happens...no changes are made....still is normal text...


all platform
Assignee: buster → jfrancis
Target Milestone: M15
bug or unimplemented feature?

we could go to beta without these.  but if it's a trivial fix, please consider
it for M12.
Status: NEW → ASSIGNED
unimplemented feature.  i'm not sure how def lists are supposed to work, so i
don't know how hard it is to do this.
Just a hint:
They are a pain, much like OL or UL. When user changes a block to DT or DD
via the Paragraph Properties, you must look for existing list container and
change it to a DL, then be sure all children are DT or DD. If there isn't one,
you must insert a DL.
Similarly when the list type is changed to DL.
I think the basic rule is only DD and DT are supposed to be children of DL.
ok, this is pretty much in line with what I thought was entailed.  I don't know
how I'm supposed to convert children to DD or DT.  I also was unaware that we
were going to have any ui that would allow changing a OL or UL to a DL.  Is that
really the case?
Target Milestone: M15 → M16
m16
Sorry, but we must support all HTML 4.0, not just what's on our toolbar!
Changing to/from LI to DT or DL should be similar to changing from OL to UL:
we have to move children to/from LI nodes. Likewise, we will have to move 
to/from DL and DT nodes. I'm writing a spec right now!
We have a similar "hole" with the Remove all styles logic as well (we don't
consider anything but B,I, and U.
Summary: defn description and term don't work → Definition list, description, and term don't work
it's great that you are working on a spec!  I dont understand the rest of your 
comment, though.  No one has marked this invalid or wontfix.  Kathy asked me to 
move some stuff to m16, if the milestone is what you are referring to.
lowering to P4; if necessary, we can push this off after beta2 (imo; based on the 
rest of Joe's bug list)
Priority: P3 → P4
updating keyword and status whiteboard to reflect that this is a beta 2 feature 
work bug that the Composer team deems a must fix for beta 2.
Severity: normal → major
Keywords: beta2
Priority: P4 → P1
Whiteboard: Composer feature work
Keywords: nsbeta2
[nsbeta2+ until 5/16]
Whiteboard: Composer feature work → [nsbeta2+ until 5/16] Composer feature work
removing self from cc-list.  editor folks have this well in control without my 
interference!
i have fix in hand for this
Whiteboard: [nsbeta2+ until 5/16] Composer feature work → (fix in hand) [nsbeta2+ until 5/16] Composer feature work
update whiteboard
Whiteboard: (fix in hand) [nsbeta2+ until 5/16] Composer feature work → (fix in hand) [nsbeta2+]
fixed
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
verified in 5/25 build.
Status: RESOLVED → VERIFIED
To tylko test
You need to log in before you can comment on or make changes to this bug.