I may be wrong but when using the Solorized theme I noticed that opening and closing {} were not highlighted the same. This of course may be intentional but it annoyed me and in the process of figuring out how to change it I discovered that the closing } did not have a scope applied to it - thus it was being highlighted as an invalid character. 

Anyway. Add the () around the end regex seems to allow the endCaptures to capture the } and apply the punctuation.section.property-list.css scope correctly and now both { and } and sytax highlighted the same way.
Merge pull request #5 from binarytales/patch-1

Closing } do not have correct scope.
Change ${«n»:«option 1»/…/«option n»/} → ${«n»|«option 1»,…,«option n»|}.
Add readme.
Move folding settings.
Disable insert color command until a solution can be found.
Add initial semantic classes.
Add more complete punctuation scopes to allow special ↩ handling.
Allow command to work in 2.0.
Use Apple choose color.
Put back the rgb convert in ruby
Add back to menu.
More properly scope `meta.property-list.css`, fixes #4 & #2.
Don’t abort when user cancels “Documentation for Property”

Using abort will show an error dialog in TextMate 2.

Closes textmate/textmate#900.
"Documentation for Property" now works for (most) CSS3 properties.

Unfortunately there is no "official" compound index of all CSS3 properties. There are several unoffical indexes, the updated list of properties in the bundle is generated from http://meiert.com/en/indices/css-properties/ (provided by Jens Meiert; seems fairly complete and up-to-date).
Correct documentation links for Text Decoration Module
Switch to tm_dialog for documentation lookup query
Move color picker changes into UI library in bundle support
Update bundle maintainer info

Fixes #9
Grammar: Match CSS 3 property names and vendor prefixes

Taken from SCSS bundle: https://github.com/MarioRicalde/SCSS.tmbundle/blob/ed7b0310682603a856a646a2db2dbcf3787cedb0/Syntaxes/SCSS.tmLanguage#L1570

There is a comment in the SCSS bundle “Reversal order is important; KEEP IT” – so I kept it :-)

However, I removed the “…|[0-9]{1,3}\%|…” part from the regex, because I think it doesn't belong here (it matches percent values, not property names).