You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is just saw that this could be a feature and not a bug, depending on what you mean as Modalhere
Because, what is being rendered is NOT a Modal, its a fully featured extension, and it is benefiting greatly from being a full screen extension.
If you think this should be a feature at least provide the option to be full screen or windowed as a prop.
This kind of visually breaking changes with no way to circumvent them, and no backwards compatibility, is not cool. If I want to use the 2024-10 version now, I can't, because everything shrinks to %50 of its size for the whole extension horizontally......
@xqwtsz sorry for the late reply here, POS on iOS is now using sheet modals, it's an app wide design change. We did version this to 2024-10 and up, so on 2024-07 it would still be full screen, as we did not want to break existing extensions on older versions. But by updating to 2024-10, on iOS it will now be in a modal sheet. This is a POS wide change, and more in line with the iOS platform, not just a UI Extension change. You'll notice that on Android it's still full screen. Apologies for the inconvenience.
Please list the package(s) involved in the issue, and include the version you are using
Also
in the
shopify.extension.toml
Describe the bug
The
Modal
component that is with the target:is rendering as a modal, and is NOT full screen as expected.
Steps to reproduce the behavior:
api_version
in theshopify.extension.toml
to2024-07
npm run dev
, everything is full screen, as expected.api_version
in theshopify.extension.toml
to2024-10
npm run dev
, modals look like modals and are not full screen.Expected behavior
Expect the Modal to be full screen.
Screenshots
shopify.extension.toml
- API Version - 2024-07 - Expectedshopify.extension.toml
- API Version - 2024-10 - BrokenThe text was updated successfully, but these errors were encountered: