Closed Bug 524284 Opened 13 years ago Closed 13 years ago

Text not visible after pressing enter in a <span>

Categories

(Core :: DOM: Editor, defect)

defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: sylvain.pasche, Assigned: smontagu)

References

()

Details

(Keywords: regression, testcase)

Attachments

(1 file)

Click on the URL for the testcase. If you press enter in a line that is contained in an inline element, the text you type next is not visible. However, that text is still inserted in the DOM.

Another testcase using Midas:
1) open http://www.mozilla.org/editor/midasdemo/
2) set font to Arial
3) press enter
4) type some text
Result: the text you type is not visible.
Assignee: nobody → smontagu
Local backout shows that this is a regression from bug 504524
Blocks: 504524
No longer blocks: 514156
Frame tree before the .data set:

    Block(body)(1)@0x1409140 {480,480,35640,2304} [state=00100000] sc=0x1409028(i=2,b=0)<
      line 0x1409548: count=1 state=inline,clean,prevmarginclean,not impacted,not wrapped,before:nobr,after:linebr[0xa140] {0,0,1,1152} <
        Inline(span)(0)@0x14094a8 next=0x1409720 next-continuation=0x1409720 {0,96,1,960} [content=0x151112b0] [overflow=0,-96,1,1152] [sc=0x1409080]<
          Frame(br)(0)@0x14094e8 {0,-96,1,1152} [content=0x151155a0]
        >
        Overflow-list<
          Text(1)@0x1409c20[0,0,T]  {0,0,0,0} [state=00000402] [content=0x1519d020] sc=0x14085e0 pst=:-moz-non-element<
            ""
          >
        >
      >
      line 0x1409760: count=1 state=inline,clean,prevmarginclean,not impacted,not wrapped,before:nobr,after:linebr[0xa100] {0,1152,1,1152} <
        Inline(span)(0)@0x1409720 prev-continuation=0x14094a8 {0,1248,1,960} [state=00000004] [content=0x151112b0] [overflow=0,-96,1,1152] [sc=0x1409080]<
          Frame(br)(2)@0x1409518 {0,-96,1,1152} [content=0x151128c0]
        >
      >
    >

Frame tree after the .data set and a reflow:

          Block(body)(1)@0x1409140 {480,480,35640,2304} [state=00100000] sc=0x1409028(i=2,b=0)<
            line 0x1409548: count=1 state=inline,clean,prevmarginclean,not impacted,not wrapped,before:nobr,after:linebr[0xa140] {0,0,1,1152} <
              Inline(span)(0)@0x14094a8 next=0x1409720 next-continuation=0x1409720 {0,96,1,960} [content=0x151112b0] [overflow=0,-96,1,1152] [sc=0x1409080]<
                Frame(br)(0)@0x14094e8 {0,-96,1,1152} [content=0x151155a0]
              >
              Overflow-list<
                Text(1)@0x1409c20[0,1,T]  {0,0,0,0} [state=00000402] [content=0x1519d020] sc=0x14085e0 pst=:-moz-non-element<
                  "a"
                >
              >
            >
            line 0x1409760: count=1 state=inline,clean,prevmarginclean,not impacted,not wrapped,before:nobr,after:linebr[0xa100] {0,1152,1,1152} <
              Inline(span)(0)@0x1409720 prev-continuation=0x14094a8 {0,1248,1,960} [state=00000004] [content=0x151112b0] [overflow=0,-96,1,1152] [sc=0x1409080]<
                Frame(br)(2)@0x1409518 {0,-96,1,1152} [content=0x151128c0]
              >
            >
          >
        >

Why do we have that text frame hanging out on the overflow list?  Why isn't the inline on the next line pulling it?  For the case when we set .data, we don't even mark the next line dirty, that I can see....
The patch for bug 523468 fixes this.
Depends on: 523468
Fixed by checkin of bug 523468.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.