Open Bug 1644680 Opened 4 years ago Updated 2 years ago

foreignObject overflow:visible not working

Categories

(Core :: SVG, defect)

77 Branch
defect

Tracking

()

People

(Reporter: breakthroughTGW, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Attached file test2.html

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36

Steps to reproduce:

set foreignObject overflow property to visible
insert elements into foreignObject after timeout 1000ms

Actual results:

elements not visible

Expected results:

elements should visible

Status: UNCONFIRMED → NEW
Component: Untriaged → SVG
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
Regressed by: 1458968
Has Regression Range: --- → yes

Not a particularly recent regression (2 years), but this definitely looks broken.

Triggering a reflow (e.g. by zooming, or modifying a property like font-size on the foreignObject) causes the missing content to pop into view.

Markus, given the range in comment 1, it looks like your patches may be responsible for this. Can you take a look?

Severity: -- → S3
Flags: needinfo?(mstange)

Hmm, the patch at https://hg.mozilla.org/mozilla-central/rev/09b3d826af11 makes me think that, since this worked before bug 1458968, it was probably working by accident.
And since bug 1557245, it "should" be working.

I suppose there's a missing reflow here that would be needed to update the visual overflow rect?
I don't know the SVG reflow code, I'm not the right person to fix this bug.

Maybe Violet is interested in giving this a spin?

Flags: needinfo?(mstange) → needinfo?(violet.bugreport)

I'm hoping this comment will revive this bug to get resolved.

1.) Go to https://whiteboard.onlinelearningsessions.com/ff_text_testing.
2.) Select the "T" tool (text), then click on the board and start typing. Note that after a few characters, the text is not rendering. A similar thing tends to happen when hitting enter to add text on the next line.
3.) Hit f12 to inspect element.
4.) Change something like font-size or color or font-family, etc. and notice that the previously typed text shows up.

Please advise if anything else is needed in order to correct this, as this bug is impacting the usage of the app that my customers use.

Looking at the reproduction case it seems like the first child of the foreignObject is always fully visible. More specifically the first block line is always visible (which most of the cases means that the first child of the first child of the first child is visible) and all the elements on different lines are not. Can we narrow it down through that?

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(violet.bugreport)

This but is still present. Please advise on when it will be fixed.

Flags: needinfo?(jwatt)

Right now there are no plans to work on this particular bug. foreignObject is low priority.

Flags: needinfo?(jwatt)

Is there a suggested workaround in the meantime, at least? This is screwing up a custom build we are using for FF users.

Increase the height or width of the foreignObject element so its contents don't overflow.

Yeah, that's not an option.

Again, steps to reproduce...
1.) Go to https://whiteboard.onlinelearningsessions.com/ff_text_testing.
2.) Select the "T" tool (text), then click on the board and start typing. Note that after a few characters, the text is not rendering. A similar thing tends to happen when hitting enter to add text on the next line.
3.) Click outside the textbox editor and notice that the previously typed text shows up.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: