Im trying to open a local HTML file that has images locally also it opens in Vanadium, Brave and Chrome but cant access the images.

Log says:
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
V MediaStore: Examining volume emulatoed;0 with name external_primary and state mounted
W HWVI : Image decoding logging dropped!
I cr_MessageMetrics: Triggered message stacking animation type 1.
W cr_ContentUriUtils: Cannot open content uri: content://media/external/downloads/1000046714

I tried turning on an off many settings like Native Code Debugging, Dynamic code loading, WebView Jit, Hardened memory allocator, Exploit protection, Access to Music and audio, Access to Photos and videos

File locations:
/Download/Html Folder/index.html
/Download/Html Folder/img/image.jpg

Which format do the image links in your HTML file have?

nothing facy and it work on any device thats not GOS. Works on windows, linux, vanilla android etc

<img src='img/image/jpg'>

also if i click to view the image in a new tab it either tried to download it and fails or opens a new tab that wont load depending on which browser im using in GOS

What happens if you add a slash at the beginning like <img src="/img/image.jpg"> ?

Wonder if the browser is sent like a sandboxed version of the folder and it doesnt copy images over, or the browser is restricted from phone media without user input like when uploading image.

Do GOS devs see these forums or is there another place to post this bug? cause anything thats not GOS it works on and in GOS every browser i tried has the same issue so its OS related

  • de0u replied to this.

    e5busbafceqe Are you in a position to include an example (hopefully a small one) so somebody could try to reproduce the issue?

      e5busbafceqe It might be good if it could be a bit smaller.

      Regardless, if it is easy to reproduce then it might well make sense to file an issue on the Vanadium issue tracker. In addition to the example, it would be good to indicate specific versions of browsers and specific versions of Android variants where the example works (build numbers, in both cases).

        Tried in:
        Vanadium version 135.0.7049.38.0
        Brave version 1.76.81
        Chrome version 132.0.6998.135
        Opera version 88.1.4661.83500
        Samsung Internet 27.0.0.79

        GrapheneOS (android 15) build 2025032500
        Seems pretty solid that its an OS issue not browser. Should i submit to Vanadium issue tracker and GOS issue tracker just in case?

        *i re-uploaded smaller images to test
        i think i cant edit my older post so ill post new link here:
        https://limewire.com/d/MavX8#lCl2PNrhMv 13.7kb

        • de0u replied to this.

          e5busbafceqe Should i submit to Vanadium issue tracker and GOS issue tracker just in case?

          Pick only one. Don't worry if it's the wrong one.

          Make sure not to use an ephemeral link.

            Opps posting in both and dont see how to delete one:
            https://github.com/GrapheneOS/os-issue-tracker/issues/5198
            https://github.com/GrapheneOS/Vanadium/issues/743
            i closed the vanadium one marked as a duplicate

            looks like i want able to upload the test zip file directly there so i didnt have to link outside

            index.html example incase someone looks back at this thread after that upload link expires:

            <html>
<body>
Image 1:
<img src="img/image.jpg">

Image 2:
<img src="img/image.png">
</body>
</html>
            • de0u replied to this.

              e5busbafceqe Opps posting in both [...]

              Why would that be the right approach?

              The time of the developers is limited and this issue is genuinely not urgent.

              e5busbafceqe looks like i want able to upload the test zip file directly there so i didnt have to link outside

              Hence my suggestion to make it smaller.