lp:~mozillateam/firefox/awesome-browser-branding

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

8. By Alexander Sack on 2009-10-19

* add "homePageSingleStartMain", "homePageImport", "homePageMigrationPageTitle" and
  "homePageMigrationDescription" to match expectations of 1.9.1 branch
  (LP: #396156)
  - update locales/en-US/brand.dtd

7. By Alexander Sack on 2009-10-19

* drop "releaseBaseURL" entity and add "logoCopyright" to match expectations of 1.9.1 branch (LP: #396156)
  - update locales/en-US/brand.dtd

6. By Fabien Tassin on 2008-10-01

* Drop the general.useragent.extra.firefox key, it is now in the firefox
  package as debian/ubuntu-abrowser.js.tmpl
  - update pref/firefox-branding.js

5. By Fabien Tassin on 2008-09-26

* Don't hardcode the Firefox version in the pref file, use %VERSION% instead
  - update pref/firefox-branding.js

4. By Alexander Sack on 2008-08-28

* ship awesome-branding content in awesome-branding.jar
  - update content/jar.mn

3. By Alexander Sack on 2008-08-28

* fix build problems by removing empty line in jar.mn
  - update content/jar.mn

2. By Alexander Sack on 2008-08-26

* awesome-branding chrome tweaks. What we assume is this:
  - firefox ships its branding content in branding.jar; we ship the same file for awesome branding
    which will then get diverted by firefox branding.jar with the trademarked bits
  - for the locales we choose a different approach as we cannot except that languages without
  translations fall back to trademarked branding. We thus add a override for the two
  localizable branding files

1. By Alexander Sack on 2008-08-26

* import initial webbrowser branding