Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upUse the current parser location for CSS error #18585
Conversation
|
Do not merge yet, waiting on Gecko try results to have a patch ready to update tests. @bors-servo try |
Use the current parser location for CSS error … rather than the start location of the current construct. This likely places the error just *after* of the unexpected token whereas before would be best, but that’s likely a much bigger change. See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861
|
|
|
@bors-servo try |
1 similar comment
|
@bors-servo try |
Use the current parser location for CSS error … rather than the start location of the current construct. This likely places the error just *after* of the unexpected token whereas before would be best, but that’s likely a much bigger change. See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/18585) <!-- Reviewable:end -->
|
|
|
@bors-servo try |
Use the current parser location for CSS error … rather than the start location of the current construct. This likely places the error just *after* of the unexpected token whereas before would be best, but that’s likely a much bigger change. See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/18585) <!-- Reviewable:end -->
|
|
|
@bors-servo try |
Use the current parser location for CSS error … rather than the start location of the current construct. This likely places the error just *after* of the unexpected token whereas before would be best, but that’s likely a much bigger change. See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/18585) <!-- Reviewable:end -->
|
|
|
@bors-servo: r=emilio |
|
|
|
|
|
@bors-servo: r- |
|
@bors-servo: r=emilio clean |
|
@bors-servo: r- |
|
@bors-servo: ping |
|
|
|
Pushed another dummy amend to hopefully get homu unstuck. @bors-servo r=emilio |
|
|
Use the current parser location for CSS error … rather than the start location of the current construct. This likely places the error just *after* of the unexpected token whereas before would be best, but that’s likely a much bigger change. See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/18585) <!-- Reviewable:end -->
|
@bors-servo: r- |
|
@bors-servo: r=emilio |
|
|
|
@bors-servo: r- |
|
Moved to #18808. |
SimonSapin commentedSep 20, 2017
•
edited
… rather than the start location of the current construct. This likely places the error just after of the unexpected token whereas before would be best, but that’s likely a much bigger change.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861
This change is