cannot read the glyph inside a button

[ousia]

Describe the bug

The attached SWF file (remove the .mov extension, since it is a Flash animation) contains a full screen button using and edit text and a variable that changes values when full or normal screen .

arrows.swf.mov

It goes fullscreen and it resizes to normal size.

Ruffle isn’t able to display the glyphs from the font when used inside a button.

If the button contains an outline, it is displayed just fine.

I’m attach a sample file (again, .mov extension has to be removed first).

outline-arrows.swf.mov

Expected behavior

Glyph from the button should be displayed, the same way the outline from the button is displayed.

The player from Adobe displays both fine.

Many thanks for your help.

Affected platform

All of them.

Operating system

Any of them.

Browser

Any of them.

Additional information

No response

[ousia]

Here is what the player from Adobe displays:

And here is what Ruffle displays:

BTW, sample images come from a slightly modified SWF file (.txt extension added to enable upload to GitHub).

[Herschel]

This is the same issue as #2181. The glyph is a text field inside a button, with a variable binding of arrow_fullscreen_text. Even though this is a v7 SWF, resolving a text field variable path should act like SWFv5, where buttons are not valid display objects, so arrow_fullscreen_text should resolve to _root.arrow_fullscreen_text, but Ruffle resolves it on the button as _root.arrow_fullscreen.arrow_fullscreen_text.

[ousia]

Many thanks for your reply, @Herschel.

So if I don’t get it wrong, this issue may be solved by #5492 (which would also fix #1561, among many others).

Many thanks for your excellent work.

[ousia]

I have realized that #6581 (comment) contains a fix to avoid the problem in newly generated SWFs.

Naming and calling the text variable as _root.arrow_fullscreen_text leaves nothing to be resolved and avoids the issue.

Since this seems to be a duplicate of a previously reported issue (#2181), I’m closing this one myself.

[ousia]

Only commenting to say it has been fixed by @michiel2005 with #12541 (huge thanks for that!).

Many thanks to @n0samu (I was aware of the fix through #11317 (comment)).