Bugzilla

Thanks for the advice :nika.

However I'd insist on my own opinion. 

Some reasons
1) it **only** affect android's part, and do nothing with other POSIX part.  I dont't think it is invive. (I mean in my opinion whatever a string could provide a fd should be treated as a path)
2) the `GeckoViewContentProtocolHandler` is used for Fenix opening PDF from third party application in Android. I used to want to reuse `GeckoViewInputStream` related code, but it's not easy to integrate. 
   [`fileURL`](https://searchfox.org/mozilla-central/rev/386c7f17b2421374930a447c9f424910551b659d/widget/nsIFilePicker.idl#169-174) is interesting, but i couldn't find anywhere in `dom/file` which this attribute is used.
3) focus on dom `File` ,  (ie create a new blobImpl for android ContentUri) , well ,that makes sense, but it is way complex to implement.


FYI: What do **Chromium for Android** think about whether `ContentUri` could be treated as a file **path**.
https://source.chromium.org/chromium/chromium/src/+/main:base/files/file_path.h;l=494

Thanks for the advice :nika.

However I'd insist on my own opinion. 

Some reasons
1) it **only** affect android's part, and do nothing with other POSIX part.  I don't think it is invasive. (I mean in my opinion whatever a string could provide a fd should be treated as a path)
2) the `GeckoViewContentProtocolHandler` is used for Fenix opening PDF from third party application in Android. I used to want to reuse `GeckoViewInputStream` related code, but it's not easy to integrate. 
   [`fileURL`](https://searchfox.org/mozilla-central/rev/386c7f17b2421374930a447c9f424910551b659d/widget/nsIFilePicker.idl#169-174) is interesting, but i couldn't find anywhere in `dom/file` which this attribute is used.
3) focus on dom `File` ,  (ie create a new blobImpl for android ContentUri) , well ,that makes sense, but it is way complex to implement.


FYI: What do **Chromium for Android** think about whether `ContentUri` could be treated as a file **path**.
https://source.chromium.org/chromium/chromium/src/+/main:base/files/file_path.h;l=494

Thanks for your advice :nika.

However I'd insist on my own opinion. 

Some reasons
1) it **only** affect android's part, and do nothing with other POSIX part.  I don't think it is invasive. (I mean in my opinion whatever a string could provide a fd should be treated as a path)
2) the `GeckoViewContentProtocolHandler` is used for Fenix opening PDF from third party application in Android. I used to want to reuse `GeckoViewInputStream` related code, but it's not easy to integrate. 
   [`fileURL`](https://searchfox.org/mozilla-central/rev/386c7f17b2421374930a447c9f424910551b659d/widget/nsIFilePicker.idl#169-174) is interesting, but i couldn't find anywhere in `dom/file` which this attribute is used.
3) focus on dom `File` ,  (ie create a new blobImpl for android ContentUri) , well ,that makes sense, but it is way complex to implement.


FYI: What do **Chromium for Android** think about whether `ContentUri` could be treated as a file **path**.
https://source.chromium.org/chromium/chromium/src/+/main:base/files/file_path.h;l=494