Bug 248784 – Avoid uint64_t overflow in Decimal::operator/()

• Component: New Bugs
• Status: RESOLVED FIXED

[Ahmad Saleem]

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!

[Sam Sneddon [:gsnedders]]

> 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?

[Radar WebKit Bug Importer]

<rdar://problem/103269252>

[Ahmad Saleem]

(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

[EWS]

Committed 258174@main (d16c8e20b19e): <https://commits.webkit.org/258174@main>

Reviewed commits have been landed. Closing PR #7908 and removing active labels.

[Brent Fulgham]

*** Bug 247514 has been marked as a duplicate of this bug. ***