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
Describe the bug
When putting a relative path into the uri field of an Image tag's source property, the image will not display, however it will take the correct amount of "space" given in the width and height of its style property.
Such an issue doesn't occur when loading from an external URL, the image appears immediately
Run with npm run dev and then modify the source uri to something like img/next.png in the case of this example. When saving that change, it should automatically apply a hotfix which makes the image actually appear
Expected behavior
The image loads from the relative path immediately
None of the above work. They all throw the exact same issue.
My current version of proton is: 2.0.4
I installed it through the proton-cli npx package.
I would really like to use this for my companies embedded solution in our factories, so I am hoping to get some basic issues resolved. Is there any better documentation on the native layer? I will need to use native libraries in SPI and other lower languages to build better high level components for our uses.
Describe the bug
When putting a relative path into the uri field of an Image tag's source property, the image will not display, however it will take the correct amount of "space" given in the width and height of its style property.
Such an issue doesn't occur when loading from an external URL, the image appears immediately
To Reproduce
Minimal example:
Run with
npm run dev
and then modify the source uri to something likeimg/next.png
in the case of this example. When saving that change, it should automatically apply a hotfix which makes the image actually appearExpected behavior
The image loads from the relative path immediately
Screenshots
Versions:
Additional context
Possibly related to #262
The text was updated successfully, but these errors were encountered: