Nathan of Guardian wrote, On 25.11.2013 07:07:
One question is that if I am implementing my own Android app (Orfox!)
around the GeckoView
Hello Nathan,
as a consultant who often had to help companies who stood before the
very same task of a customized, specialized browser, and the very same
question of Firefox vs. xulrunner, I recommend you to keep Firefox and
not GeckoView as base.
What you want is a browser, not just displaying a single webpage. The
difference are urlbar, tabs, bookmarks, cookies, and all the UI. You
don't want cookies, but you do want urlbar, tabs, bookmarks etc.. This
is non-trivial, the Firefox Android team puts a lot of effort into this
UI, and it changes often.
I think you are better advised to find ways to disable unwanted features
like cookies and favicons than to re-implement the browser UI.
If this proves to be hard, please do file bugs and have this discussion
here on the mailing list. Even though it may seem to you and the Firefox
team that you're the only usecase where such adaptions are necessary, I
can assure you that you are not, and that things like "disable cookies",
"disable javascript", "disable content from third party sites", "disable
favicons" etc. are essential for a very wide arrange of usecases. Most
of them are in internal applications or in specialized applications,
what was sometimes called "dark matter", but there are tons of such
customizations. Therefore, given that they are common, such adaptions
should be easy in Firefox, and if they are not, they should be made so.
Your endeavor is very useful. Please keep it up, and I hope the Firefox
Android team will support you with 1) pointers to relevant code and
design, 2) accepting your patches.
Keep it up,
Ben
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
