This repository was archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
Return the css property value range in getInfoAtPos() api. #7390
Merged
Merged
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e489b36
Return the property value range in getInfoAtPos() api.
RaymondLim d82b043
simple unit test
JeffryBooher 045f312
'enhanced' the test data
JeffryBooher 241352b
updated unit test data
JeffryBooher 0b6747d
Merge branch 'master' into rlim/range-in-css-info
JeffryBooher a4465a6
update range unit tests
JeffryBooher 14987bb
Fix all CSS Context Info unit tests by adding range info.
RaymondLim d5b8102
rtc: spelling errors
JeffryBooher 870e99a
Handle ranges for empty property values and fix some more unit tests.
RaymondLim 99dbf8c
Fix another feedback.
RaymondLim File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| /* */ | ||
|
|
||
| .foo { | ||
| shape-inside: circle(0 | ||
| at | ||
| 0 0 | ||
| ); | ||
|
|
||
| shape-inside: circle (0px | ||
| at | ||
| 0px | ||
|
|
||
| 0px | ||
| ); | ||
|
|
||
| shape-inside: polygon(0 0, | ||
| 100px | ||
|
|
||
| 0, | ||
| 100px 100px | ||
|
|
||
|
|
||
| ); | ||
|
|
||
|
|
||
| shape-inside: | ||
| polygon( | ||
|
|
||
|
|
||
| nonzero, | ||
| 0 0, | ||
| 100px | ||
| 0, | ||
| 100px | ||
|
|
||
| 100px | ||
| ); | ||
| } | ||
|
|
||
|
|
||
|
|
||
| @keyframes colorize { | ||
| 0% { | ||
| -webkit-filter: grayscale(100%); | ||
| } | ||
| 100% { | ||
| -webkit-filter: | ||
|
|
||
|
|
||
| grayscale | ||
| ( 0 % ) | ||
|
|
||
| ; | ||
| } | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that this might be better
while (TokenUtils.moveNextToken(startCtx) && !startCtx.token.string.trim());but I'm not sure if crockford will like it.another thing that i'm wondering if
TokenUtils.moveNextToken()returns false then we fall through and we're using the property name as the thing returned. Perhaps that needs a unit test in the case of a malformed property at the end of the file.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, linter will complain on the empty block. And you're mistaken with the direction. We're scanning forwards and not backwards here.