Skip to content
Snippets Groups Projects
  1. May 29, 2023
    • Igor Oliveira's avatar
      Bug 23104: Add a default line height compensation · 0ac9d766
      Igor Oliveira authored and Pier Angelo Vendrame's avatar Pier Angelo Vendrame committed
      Many fonts have issues with their vertical metrics. they
      are used to influence the height of ascenders and depth
      of descenders. Gecko uses it to calculate the line height
      (font height + ascender + descender), however because of
      that idiosyncratic behavior across multiple operating
      systems, it can be used to identify the user's OS.
      
      The solution proposed in the patch uses a default factor
      to be multiplied with the font size, simulating the concept
      of ascender and descender. This way all operating
      systems will have the same line height only and only if the
      frame is outside the chrome.
      0ac9d766
    • Pier Angelo Vendrame's avatar
      Bug 41116: Normalize system fonts. · a3491594
      Pier Angelo Vendrame authored
      System fonts are an enormous fingerprinting vector.
      Even with font allow lists and with our custom configuration on Linux,
      which counter metrics measurements, getComputedStyle leaks several
      details.
      This patch counters both these kinds of attacks.
      a3491594
  2. Feb 02, 2023
  3. Feb 04, 2023
  4. Jan 23, 2023
  5. Dec 29, 2022
  6. Dec 27, 2022
  7. Nov 09, 2022
  8. Oct 05, 2022
  9. Sep 13, 2022
  10. Sep 19, 2022
    • Daniel Holbert's avatar
      Bug 1786910: Ignore 'align-content' when determining the aligned static... · 4d1d8215
      Daniel Holbert authored
      Bug 1786910: Ignore 'align-content' when determining the aligned static position of abspos flex children. r=TYLin a=RyanVM
      
      Before this patch, we honored `align-content` (in combination with
      `align-self`) for cross-axis alignment for abspos flex children **in cases
      where the flex container was multi-line**. This was a bit weird, but was
      required by the spec, and made some sense in the spirit of aligning the abspos
      box as if it were the sole flex item in a flex container.
      
      Now the CSSWG has resolved in [1] to simplify things by just ignoring
      `align-content` for abspos flex children. So, this patch updates us in
      accordance with this change. Such items now only have to look at `align-self`
      for cross-axis alignment to determine their static position in their flex
      container.
      
      Before this commit, we had a bunch of WPT tests to check the impact of every
      align-content value, with all of the various flavors of directionality.  Now
      that align-content has *no effect* in any of these cases, all of these tests
      become pretty trivial and redundant.  Rather than carrying them all forward
      with trivial "no impact" expectations for each scenario, I've just updated the
      first/simplest such test to expect no-behavioral-impact and I've removed the
      rest.
      
      [1] https://github.com/w3c/csswg-drafts/issues/7596#issuecomment-1225952646
      
      Differential Revision: https://phabricator.services.mozilla.com/D157571
      4d1d8215
  11. Sep 12, 2022
  12. Sep 06, 2022
  13. Aug 29, 2022
  14. Jul 05, 2022
  15. Jul 12, 2022
  16. Jul 29, 2022
  17. Jul 20, 2022
  18. Aug 03, 2022
  19. Jul 12, 2022
  20. Jul 11, 2022
  21. Jun 21, 2022
  22. Jun 24, 2022
  23. Jun 07, 2022
  24. Jun 20, 2022
  25. Jun 15, 2022
  26. Jun 09, 2022
  27. Jun 08, 2022
  28. Jun 07, 2022
  29. May 31, 2022
  30. May 29, 2022
  31. May 28, 2022
  32. May 27, 2022
  33. May 26, 2022
Loading