Closed Bug 1126650 Opened 5 years ago Closed 5 years ago

htmlrunner should have its own chrome files

Categories

(Core :: General, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED WONTFIX

People

(Reporter: paul, Unassigned)

References

Details

htmlrunner uses b2g.js. We could add plenty of `ifdef MOZ_HTMLRUNNER` in b2g.js, but I think it would be easier if we could use a different file.
Paul, I actually introduced that in bug 1126573
Yes, just saw that. But doesn't it append another file? We don't want to keep b2g.js.
I haven't made my mind yet on that. We can either append, or fork. In general I'd like to not fork when possible.
So actually, I think we want our own chrome files.

Here is what comes with B2G:

▾ chrome/
  ▾ content/
    ▾ devtools/
        debugger.js                 ---- Needs small tweaks
        adb.js                      ---- Not useful
        hud.js                      ---- Not useful
    ▸ images/                       ---- Not useful
    ▸ test/
      arrow.svg                     ---- Not useful
      desktop.css                   ---- Not useful
      desktop.js                    ---- Not useful
      runapp.js                     ---- Not useful
      screen.js                     ---- Not useful
      touchcontrols.css             ---- Not useful
      content.css                   ---- Needs rewrite
      shell.html                    ---- Needs to be stripped-down
      shell.js                      ---- Needs to be stripped-down
      settings.js                   ---- Need serious tweaking
      aboutCertError.xhtml          ---- Useful
      ErrorPage.js                  ---- Useful
      netError.css                  ---- Useful
      shell.css                     ---- Useful (very small)
      identity.js                   ---- I don't know

Doing all of that with ifdefs will be difficult.
Summary: htmlrunner should have its own preference file → htmlrunner should have its own chrome files
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.