2 ms·
We just gave up on getting our addon into the Mozilla store and distribute it directly via our website. Their process is not worth the hassle. We were rejecte
by ctide 12y ago
We just gave up on getting our addon into the Mozilla store and distribute it directly via our website. Their process is not worth the hassle. We were rejected because:
1) This version contains binary, obfuscated or minified code. We need to review all of your source code in order to approve it.
We included all of the source, but we didn't explain how to setup a local environment to build handlebars templates, setup grunt, etc. so apparently source is not good enough on it's own. The reviewers have to understand enough about your app to build it themselves. Writing enough documentation so that someone in 30 days can hopefully glean everything they need (with no understanding of your app, or structure) without them being able to ask you questions is absurd.
2) Please use the CSS 'text-overflow' property rather than trying to deal with overflow via `innerHTML` modification.
We have multiline text we need truncated and displayed correctly. This means not having a random floating ellipsis at the end of the div, and it means we can't use text-overflow.
Mozilla's addon policy is just hostile, period. It doesn't have anything to do with open source.