Bugzilla

(In reply to Valentin Gosu [:valentin] (he/him) from comment #12)
> (In reply to [:owlish] 🦉 PST from comment #11)
> > This is the first time I hear that libxul is not loaded.... Without libxul neither GeckoView, nor Fenix would be able to function. 
> 
> I was under the impression that we might need to parse URLs before loading libxul, such as for processing intents? For example in bug 1880491.
> If that's not a case we care too much about, then calling into Gecko via JNI to create a nsIURI is a great option, and the option that is most likely to avoid future mismatches between GV and Gecko.

Ah, ok - yes, that makes sense. Yes, indeed, there are some situations where we need to parse a URL before Gecko would get a chance to load. However, I think we need to try and see if we can find a less dramatic solution than extracting nsIURI into a separate library. Christian think it should be possible.

I also asked Christian about the difference in standards utilized for parsing Gecko vs AC - he said there was no particular reason for that, was not an intentional decision, so there is no reason for us to continue to stick with rfc3986.

Valentin, does Gecko use WHATWG everywhere? Thanks!

(In reply to Valentin Gosu [:valentin] (he/him) from comment #12)
> (In reply to [:owlish] 🦉 PST from comment #11)
> > This is the first time I hear that libxul is not loaded.... Without libxul neither GeckoView, nor Fenix would be able to function. 
> 
> I was under the impression that we might need to parse URLs before loading libxul, such as for processing intents? For example in bug 1880491.
> If that's not a case we care too much about, then calling into Gecko via JNI to create a nsIURI is a great option, and the option that is most likely to avoid future mismatches between GV and Gecko.

Ah, ok - yes, that makes sense. Yes, indeed, there are some situations where we need to parse a URL before Gecko would get a chance to load. However, I think we need to try and see if we can find a less dramatic solution than extracting nsIURI into a separate library. Christian thinks it should be possible.

I also asked Christian about the difference in standards utilized for parsing Gecko vs AC - he said there was no particular reason for that, was not an intentional decision, so there is no reason for us to continue to stick with rfc3986.

Valentin, does Gecko use WHATWG everywhere? Thanks!