juanepaktho / j.nathasit

J.nathasit

j.nathasit's Issues

## Bug report

Bug report

Describe the bug
A clear and concise description of what the bug is.

Steps to reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. '...'
3. See error or incorrect behavior

Expected behavior

A clear and concise description of what you expected to happen.

---

Additional context

Add any other context about the problem here.

---

Flutter doctor

Run flutter doctor and paste the output below:

Click To Expand

PASTE OUTPUT INSIDE HERE

---

Flutter dependencies

Run flutter pub deps -- --style=compact and paste the output below:

Click To Expand

PASTE OUTPUT INSIDE HERE

---

Originally posted by @id18522096554 in firebase/flutterfire#4480

<!-- Thank you for using Flutter!

Steps to Reproduce

1. Run flutter create bug.
2. Update the files as follows: ...
3. ...

Expected results:

Actual results:

Logs

Originally posted by @Juanepaktho in flutter/flutter#73009

JSBox 版本: 2.13.0 (1165) TestFlight 下载

JSBox 版本: 2.13.0 (1165) TestFlight 下载

我理解 HomeWidget 的布局 'spacer' 对应的是 SwiftUI 里面的 Spacer 吧？但是似乎 JSBox 里面的 'spacer' 最小宽度很大的样子，在有足够的空间的情况下，能把 text 挤压到不能显示全。
比如，如下图，

对应的代码是:

$widget.setTimeline({
        policy: {
            never: true,
        },
        render: ctx => {
            console.info(`size: {${ctx.displaySize.width}, ${ctx.displaySize.height}} `)
            return {
                type: 'zstack',
                views: [
                    {
                        type: 'hstack',
                        props: {
                            alignment: 'center',
                        },
                        views: [
                            {
                                type: 'vstack',
                                props: {
                                    alignment: 'leading',
                                },
                                views: [
                                    {
                                        type: 'text',
                                        props: {
                                            text: 'PlaceHolder12345',
                                            lineLimit: 1,
                                        }
                                    },
                                ]
                            },
                            {
                                type: 'spacer',
                            },
                            {
                                type: 'vstack',
                                props: {
                                    alignment: 'leading'
                                },
                                views: [
                                    {
                                        type: 'text',
                                        props: {
                                            lineLimit: 1,
                                            text: 'PlaceHolder',
                                        }
                                    }
                                ]
                            },
                        ]
                    }
                ]
            }
        }
    });

我尝试在 Xcode 下 Widget 类似的代码是不是有问题，Xcode 那边 Spacer 显示的挺正常的，如下图：

对应的代码如下:

Originally posted by @MichaelPei in https://github.com/cyanzhong/jsbox-issues/issues/90

This is the tracking issue for **Accessibility** in AVM1. We will check off each item of progress as appropriate, and fill in any relevant or missing information as we continue development of Ruffle.

This is the tracking issue for Accessibility in AVM1. We will check off each item of progress as appropriate, and fill in any relevant or missing information as we continue development of Ruffle.

Legend

Each checkbox is independent of another. It's entirely possible for something to be tested but not exist yet, or for us to believe that it's completely functional but we haven't made enough tests to prove it.

"Property Exists"

This means the item exists, but may not necessarily be fully implemented.

"Has Test Coverage"

This means that we believe that we have a good test coverage of this item, regardless of if those tests pass. It's okay to have tests available but not implement the item yet.

"Completely Functional"

This means we believe that the item is completely implemented, and no more work needs to be done towards making it functional.

Accessibility

Static Methods

isActive()

• Property Exists
• Has Test Coverage
• Completely Functional

sendEvent(mc, childID, event, isNonHtml)

• Property Exists
• Has Test Coverage
• Completely Functional

updateProperties()

• Property Exists
• Has Test Coverage
• Completely Functional

Originally posted by @Dinnerbone in ruffle-rs/ruffle#239