Skip to content
GitLab
  1. 26 Jul, 2018 1 commit
  3. 25 Jul, 2018 4 commits
  5. 24 Jul, 2018 2 commits
  7. 26 Jul, 2018 3 commits
  9. 25 Jul, 2018 1 commit
  11. 24 Jul, 2018 1 commit
  13. 26 Jul, 2018 1 commit
  15. 17 Jul, 2018 1 commit
  17. 16 Jul, 2018 1 commit
  19. 25 Jul, 2018 1 commit
    • Jim Chen's avatar
      Bug 1478445 - Adopt and detach child process FDs; r=rbarker · 7a53328e
      Jim Chen authored 
      Use adoptFd and detachFd so we don't duplicate FDs unnecessarily. Also
fix a bug where we didn't close the pref FDs.

MozReview-Commit-ID: Gugcyi4cj7V

--HG--
extra : rebase_source : 035f62d8ba4d1ec964d5b7f7556bae7164ab78b3
      7a53328e
  21. 23 Jul, 2018 1 commit
    • Masayuki Nakano's avatar
      Bug 1477898 - Make AutoRestoreEditorState not call EditorBase::SetFlags()... · 5f1e6f2a
      Masayuki Nakano authored 
      Bug 1477898 - Make AutoRestoreEditorState not call EditorBase::SetFlags() since the virtual call cost appears in profile r=m_kato

Unfortunately, EditorBase::SetFlags() is virtual call even though
AutoRestoreEditorState always works only with TextEditor (the method is
overridden only by HTMLEditor).  And AutoRestoreEditorState is a hot path
when <input>.value or <textarea>.value is set a lot.

Fortunately, EditorBase::Flags() can be an inline method.  So, we can make
both constructor and destructor of the class check if it'll change flags
actually.

Additionally, this patch fixes nsTextEditorState::PrepareEditor() too.

MozReview-Commit-ID: 7S4hLRRrbfB

--HG--
extra : rebase_source : 3c3e7438cd7e6c9853e5cf876277d7459b86c343
      5f1e6f2a
  23. 26 Jul, 2018 2 commits
  25. 25 Jul, 2018 1 commit
    • Matthew Noorenberghe's avatar
      Bug 1476204 - Handle autofill record update state changes in the unpriv. PR forms. r=jaws · 46813c48
      Matthew Noorenberghe authored 
      This is easier to understand as we don't have to round-trip the whole success and error states to the privileged wrapper which could potentially lead to stale state changes.
This is also much simpler for the basic-card-form as it doesn't need a lot of the complexity of the previous implementation.

* Move selectedStateKey from page to address-page since it doesn't apply to basic-card-page

MozReview-Commit-ID: B4kiZNWElGI

--HG--
extra : rebase_source : 183a3bd44ed33566fccdc024eabdccef83554d50
      46813c48
  27. 24 Jul, 2018 2 commits
  29. 25 Jul, 2018 1 commit
    • Matthew Noorenberghe's avatar
      Bug 1476204 - Check Luhn algorithm in the basic-card-form and in storage and... · f5f3467e
      Matthew Noorenberghe authored 
      Bug 1476204 - Check Luhn algorithm in the basic-card-form and in storage and disable save button when invalid. r=jaws

* Provide an cc-exp-year option to match cc-exp-month
* Make cc-number and cc-name required in the basic-card-form
* Disable the basic-card-page save button when the form is invalid.

MozReview-Commit-ID: LjzsnAKJp6R

--HG--
extra : rebase_source : 467fa09ea07c0234e1839b6dfd7e53375c118104
      f5f3467e
  31. 20 Jul, 2018 1 commit
  33. 24 Jul, 2018 1 commit
  35. 25 Jul, 2018 1 commit
  37. 23 Jul, 2018 2 commits
  39. 13 Jul, 2018 1 commit
    • Dipen Patel's avatar
      Bug 1475647 - Remove nsISSLStatusProvider interface. r=baku,Gijs,jchen,jryans,keeler,mcmanus · 7641beb1
      Dipen Patel authored 
      - Access nsISSLStatus directly as a member of nsITransportSecurityInfo
and nsISecureBrowserUI.  This is part of a larger effort to consolidate
nsISSLStatus and nsITransportSecurityInfo.
- The TabParent implementation of GetSecInfo will always return null.
- Removed unnecessary QueryInterface calls
- Style adherence updates

MozReview-Commit-ID: Dzy6t2zYljL

--HG--
extra : rebase_source : 9c400bed3c9d29a186fc987c9bd0ffceb37bfd94
      7641beb1
  41. 08 Jul, 2018 1 commit
  43. 30 Jun, 2018 1 commit
    • Jan Beich's avatar
      Bug 1473732 - Base default number of OMTP workers on the number of logical CPU cores. r=rhunt · 061b467f
      Jan Beich authored 
      system-info is a stub on Tier3 platforms while physical vs. logical
difference only matters for hyper-threading. As hyper-threading
is usually available on CPUs with more than 2 physical cores this
change has no impact there as the default is clamped to [1, 4].
However, on Intel i3-* CPUs with 2 physical and 4 logical cores this
bumps the default from 1 to 3.

MozReview-Commit-ID: 1Yh8rJL2JcN

--HG--
extra : rebase_source : 77613cbb99c14f19217592080bfd51ea2194422b
      061b467f
  45. 19 Jul, 2018 1 commit
  47. 25 Jul, 2018 8 commits