1. 31 Aug, 2017 1 commit
  2. 02 Jun, 2017 1 commit
  3. 31 May, 2017 3 commits
  4. 30 May, 2017 4 commits
  5. 23 May, 2017 1 commit
  6. 20 May, 2017 1 commit
  7. 18 May, 2017 2 commits
  8. 16 May, 2017 1 commit
  9. 22 Mar, 2017 4 commits
  10. 17 Mar, 2017 1 commit
  11. 16 Mar, 2017 3 commits
  12. 27 Feb, 2017 1 commit
  13. 17 Feb, 2017 2 commits
  14. 08 Feb, 2017 1 commit
  15. 19 Dec, 2016 1 commit
  16. 14 Dec, 2016 1 commit
    • Federico Mena Quintero's avatar
      Be explicit about how stop-color and stop-opacity are inherited · c32694be
      Federico Mena Quintero authored
      These can live in the <stop> element attributes, or in its style="..."
      attribute.
      
      Neither of them inherits by default; they have to be explicitly
      specified as "inherit" to do that.
      
      Inheritance is from the gradient's parent element, not from where it is
      referenced, hence the call to rsvg_state_reconstruct().
      
      Also, stop-color can be currentColor.
      
      We now have explicit enums to indicate all of these cases.  Previously,
      all the meanings were overloaded into state->has_stop_color and
      state->has_stop_opacity, and those didn't handle all cases correctly.
      
      Added the hexchat.svg icon to the tests, which is how I caught the lack
      of proper handling for style="stop-color: ...;".
      c32694be
  17. 22 Nov, 2016 2 commits
  18. 16 Nov, 2016 1 commit
  19. 11 Nov, 2016 2 commits
  20. 09 Nov, 2016 7 commits