| Summary: | Improve intersection precision in FloatPoint | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | mattwoodrow, mmaxfield, simon.fraser, webkit-bug-importer, zalan |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Ahmad Saleem
2023-01-18 16:00:47 PST
It is inspired from this - https://github.com/servo/skia-snapshots/blob/master/skia/experimental/Intersection/LineIntersection.cpp#L43 as per commentary on Review and also from https://en.wikipedia.org/wiki/Line–line_intersection. There were three tests requiring baseline after this: One of them - related to border: https://jsfiddle.net/nmL1g95c/show In Safari, we have hairline gaps in Safari 16.2 & STP161 while we don't have those in Chrome Canary 111. This seems like a good change. If we merge it, does it cause any tests to pass? It looks like it caused some Chrome tests to pass for them. (In reply to Myles C. Maxfield from comment #3) > This seems like a good change. > > If we merge it, does it cause any tests to pass? It looks like it caused > some Chrome tests to pass for them. I haven't run it through EWS or any specific test suite but I have it as local testing on my local build since past two days and I tried to look into border radius, border shadow test cases with hairline gaps but it seems that it does not improve anything across them but it is just cleaner code as of right now. Let me do PR in Draft and see if anything pop-up. Thanks! Committed 259574@main (4ecebb76cee1): <https://commits.webkit.org/259574@main> Reviewed commits have been landed. Closing PR #9257 and removing active labels. |