Closed
Bug 840928
Opened 11 years ago
Closed 10 years ago
Transition to a WebKit engine
Categories
(Firefox OS Graveyard :: Gaia, defect)
Firefox OS Graveyard
Gaia
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: beta, Unassigned)
References
()
Details
(Keywords: compat, privacy-review-needed, student-project, Whiteboard: [good second bug] [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st])
Attachments
(1 file)
547 bytes,
patch
|
Yoric
:
feedback+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20130212 Firefox/20.0 Build ID: 20130212042017 Steps to reproduce: Following on from the recent announcement by Opera, http://www.opera.com/press/releases/2013/02/13/ and upcoming changes to Firefox: http://blog.pearce.org.nz/2013/02/h264aacmp3-support-now-enabled-by.html http://mikeconley.ca/blog/2013/02/12/making-australis-tab-animations-faster/ We might as well join the club, stop innovating and make a monoculture out of it. /s
Reporter | ||
Updated•11 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Whiteboard: [parity-opera] [parity-chrome] [parity-safari]
Comment 1•11 years ago
|
||
No.
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Comment 2•11 years ago
|
||
Damn, I had a patch!
Comment 3•11 years ago
|
||
We could just run WebKit in a tab using emscripten.
Clearly belongs in Core.
Component: Untriaged → General
Product: Firefox → Core
Comment 5•11 years ago
|
||
Maybe not. We could port WebKit to B2G using Emscripten.
Component: General → Gaia
Product: Core → Boot2Gecko
Version: 20 Branch → unspecified
Adding azakai for a feasibility assessment.
Flags: needinfo?(azakai)
Comment 7•11 years ago
|
||
Well, if you can port Qt, I guess you can port anything... http://vps2.etotheipiplusone.com:30176/redmine/emscripten-qt-examples/scribble.html But, please no.
Flags: needinfo?(azakai)
Updated•11 years ago
|
Summary: Transition to a WebKit engine → Transition to a WebKit engine (Read this you craps)
Comment 8•11 years ago
|
||
I have faith in Emscripten! /be
Comment 9•11 years ago
|
||
Needs more discussion of possibilities!
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WONTFIX → ---
Updated•11 years ago
|
Keywords: privacy-review-needed,
student-project
Updated•11 years ago
|
Whiteboard: [parity-opera] [parity-chrome] [parity-safari] → [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st]
Comment on attachment 713443 [details] [diff] [review] patch v1.0 Review of attachment 713443 [details] [diff] [review]: ----------------------------------------------------------------- Good start, but needs some testing.
Attachment #713443 -
Flags: feedback+
Updated•11 years ago
|
Whiteboard: [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st] → [good first bug][parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st]
I this requires some prior Mozilla experience.
Whiteboard: [good first bug][parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st] → [good second bug][parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st]
Updated•11 years ago
|
Keywords: compat
Whiteboard: [good second bug][parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st] → [mentor=opera] [good second bug] [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st]
Comment 12•11 years ago
|
||
Maybe we could get Google to fund this for Summer of Code?
Comment 13•11 years ago
|
||
This is clearly add-on material.
Comment 14•11 years ago
|
||
If we used the NPAPI instead, we could get out of process embedding for free.
@jdm Do you want to compile NPAPI with Emscripten?
Comment 16•11 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #13) > This is clearly add-on material. You are a genius. All we need to do is make Chrome Frame compatible with Firefox and then redirect all users to http://www.google.com/chromeframe when their browser is opened. If users fail to download and install it we can refuse to let them navigate to any other URL until they do.
Comment 17•11 years ago
|
||
I think the simplest solution is to simply slap a Firefox sticker on Chromium and head to the bar. I'm buying. :)
Comment 18•11 years ago
|
||
(In reply to Lawrence Mandel [:lmandel] from comment #17) > I think the simplest solution is to simply slap a Firefox sticker on > Chromium and head to the bar. I'm buying. :) I was actually going to suggest to Gerv that I found the solution all of our web compatibility problems in this bug. But that works too.
Comment 19•11 years ago
|
||
Unfortunately, many of our web compatibility problems would still remain. I've been privately informed by the Chrome team that if we change our User Agent to copy theirs (which would be necessary for full web compatibility) then they will sue us for trademark infringement. I therefore propose that we developer 1024 possible different user agent strings which are similar but not identical to the Chrome one and test them by developing a random user agent string picker and shipping it directly on the release channel, using the relative volume of screams of anguish on input.mozilla.org to decide which one to use permanently. Gerv
Summary: Transition to a WebKit engine (Read this you craps) → Transition to a WebKit engine
Updated•11 years ago
|
Comment 20•11 years ago
|
||
We could sue them for using "Mozilla" in their User-Agent too as it's also trademark infringement ;)
Comment 21•11 years ago
|
||
Virtual_ManPL: Shh! Don't give away our legal strategy! Gerv
Comment 22•11 years ago
|
||
Any plans to adopt Blink instead?
Comment 23•11 years ago
|
||
(In reply to Please Ignore This Troll from comment #22) > > Any plans to adopt Blink instead? We already are: see about:config "browser.blink_allowed" which is set to 'true'. Set this to 'false' if you want to switch back to using Gecko.
Updated•11 years ago
|
Whiteboard: [mentor=opera] [good second bug] [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st] → [good second bug] [parity-opera] [parity-chrome] [parity-safari] [oh-great-now-we-have-to-keep-this-bug-alive-until-april-1st]
Comment 24•10 years ago
|
||
OK, I think the joke has run its course.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•