248784 2022-12-05 14:06:16 -0800 Avoid uint64_t overflow in Decimal::operator/() 2024-01-23 16:52:16 -0800 1 1 1 Unclassified WebKit New Bugs Safari Technology Preview Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=247514 InRadar P2 Normal --- 1 ahmad.saleem792 webkit-unassigned cdumez darin rniwa webkit-bug-importer oldest_to_newest 1916782 0 ahmad.saleem792 2022-12-05 14:06:16 -0800 Hi Team, While going through Blink's commit, I found another failing test case: Blink Commit - https://src.chromium.org/viewvc/blink?view=revision&revision=191294 Failing Test Case - https://jsfiddle.net/rerich/pn1o3wvn/ (^ First range is at 'zero' compared to Chrome / Blink). Just wanted to raise this bug so it can be merged or fixed. Unfortunately, I will not be able to do it because the test is in C++ and I am not able to do it in this bug 247514, appreciate if someone can fix both in one go. Thanks! 1917572 1 gsnedders 2022-12-08 06:45:52 -0800 > Unfortunately, I will not be able to do it because the test is in C++ While it's not ideal, importing the failing test case linked above (with input type=range), converting it to a reftest, would be better than nothing. Unless this ends up exposed through the DOM API? 1918599 2 webkit-bug-importer 2022-12-12 14:07:16 -0800 <rdar://problem/103269252> 1920789 3 ahmad.saleem792 2022-12-20 08:40:32 -0800 (In reply to Sam Sneddon [:gsnedders] from comment #1) > > Unfortunately, I will not be able to do it because the test is in C++ > > While it's not ideal, importing the failing test case linked above (with > input type=range), converting it to a reftest, would be better than nothing. > Unless this ends up exposed through the DOM API? Managed to figure out the ref-test. PR - https://github.com/WebKit/WebKit/pull/7908 1920976 4 ews-feeder 2022-12-20 18:49:32 -0800 Committed 258174@main (d16c8e20b19e): <https://commits.webkit.org/258174@main> Reviewed commits have been landed. Closing PR #7908 and removing active labels. 2007067 5 bfulgham 2024-01-23 16:52:16 -0800 *** Bug 247514 has been marked as a duplicate of this bug. ***