Skip to content

[css-typed-om] Remove issue #310 from text. #481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 17, 2017
Merged

[css-typed-om] Remove issue #310 from text. #481

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3826b7
Remove issue 310
darrnshn Oct 16, 2017
ce3d645
Move issue to css-typed-om 2
darrnshn Oct 17, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions css-typed-om-2/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,3 +31,5 @@ Issue(142): Do we want a font value class? How about a FontWeightValue (for 100,
Issue(144): Add more CSS3 properties. This table currently only contains CSS2.1 properties and CSS3 properties alphabetically to border-radius.

Issue(136): Need an array-buffer custom property type.

Issue(310): consider using properties in addition to get/set.
2 changes: 0 additions & 2 deletions css-typed-om/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -375,8 +375,6 @@ Issue(268): stringification

Issue(276): interaction with custom properties

Issue(310): consider using properties in addition to get/set

Computed {{StylePropertyMapReadOnly}} objects {#computed-stylepropertymapreadonly-objects}
--------------------------------------------------------------------------

Expand Down