1423876 - webextension not support on mips

Status: UNCONFIRMED

(WebExtensions :: General, defect, P5)

Description

[huangwenjun06]

Attachment: console_error_info

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce:

about:debugging and temporary install addon.
example:https://github.com/mdn/webextensions-examples/tree/master/notify-link-clicks-i18n


Actual results:

webextension not support, addon could not used


Expected results:

webextension should support.

Terminal Info:Error processing default_locale: An unexpected property was found in the webExtension manifest.

WebConsole Info: see attachment file console_err_info.jpg

Comment 1

[huangwenjun06]

on x86 platform: webextension support.
on mips64 platform: webextension not support.

Comment 2

[Kris Maglione [:kmag]]

MIPS is not officially supported, but we'd be willing to take a non-invasive patch for this.

Comment 3

[Andrew Swan [:aswan]]

I'm not sure what's going on but mips isn't a platform that we officially support and we don't have access to a mips machine to troubleshoot this..  From the first visible line in your screenshot, though it looks like there might be other build/packaging issues going on.

Comment 4

[huangwenjun06]

I just use mach build command to build firefox52. 

I didthe following experiment
1）firefox52 is failed, but firefox54 is ok.
2）Replace file (toolkit/components/extensions/Schemas.jsm)  from firefox54 to firefox52 is ok too.
3）I annotate line 721 (toolkit/components/extensions/Schemas.jsm) is ok too.
 
  static checkSchemaProperties(schema, path, extra = []) {
    let allowedSet = new Set([...this.EXTRA_PROPERTIES, ...extra]);
    let log = Log.repository.getLogger("MyExtension.MyClass");
    log.level = Log.Level.Warn;
    log.addAppender(new Log.ConsoleAppender(new Log.BasicFormatter()));
    log.addAppender(new Log.DumpAppender(new Log.BasicFormatter()));

    for (let prop of Object.keys(schema)) {
     //log.warn("Here is an Info", {"prop": prop});
     //if (!allowedSet.has(prop)) {
     //   throw new Error(`Internal error: Namespace ${path.join(".")} has invalid type property "${prop}" in type "${sch
ema.id || JSON.stringify(schema)}"`);
     // }
    }
  }

could somebody give me some instruction to solve this problem?

Comment 5

[Kris Maglione [:kmag]]

I'm sorry, but you're more or less on your own here unless you can reproduce the problem on a supported platform.

Comment 6

[Firefox Bug Husbandry Bot]

Bulk move of bugs per https://bugzilla.mozilla.org/show_bug.cgi?id=1483958