We are no longer offering accounts on this server. Consider https://gitlab.freedesktop.org/ as a place to host projects.

  1. 19 Jan, 2011 1 commit
  2. 18 Jan, 2011 7 commits
  3. 17 Jan, 2011 2 commits
  4. 10 Jan, 2011 1 commit
  5. 08 Jan, 2011 5 commits
  6. 07 Jan, 2011 6 commits
  7. 06 Jan, 2011 6 commits
  8. 05 Jan, 2011 10 commits
  9. 04 Jan, 2011 2 commits
    • Evan Prodromou's avatar
      3dcf8f1e
    • Brion Vibber's avatar
      Fix ticket #2181: Can't save #000000 (black) in color fields on design page · af1cbc6f
      Brion Vibber authored
      It seems to have actually been saving correctly, but the update of the colors on the form success page wasn't working properly.
      When a design object is pulled out of the database, the numeric fields are read in as strings, so black comes back as "0".
      But, when we populate the new object and then stick it live, we've populated it with actual integers; with memcache on these might live for a while in the cache...
      
      The fallback code in Design::toWebColor() did a check ($color == null) which would be false for the string "0", but counts as true for the *integer* 0.
      Thus, the display code would initially interpret the correctly-saved black color as "use default".
      
      Changing the check to === against null and "" empty string avoids the false positive on integers, and lets us see our nice black text immediately after save.
      af1cbc6f