[Webkit-unassigned] [Bug 253409] Failing Tests minlength and maxlength in <textarea>

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=253409

--- Comment #10 from Ahmad Saleem <ahmad.saleem792 at gmail.com> ---
(In reply to Chris Dumez from comment #9)
> (In reply to Ahmad Saleem from comment #8)
> > (In reply to Ahmad Saleem from comment #7)
> > > (In reply to Chris Dumez from comment #6)
> > > > (In reply to Ahmad Saleem from comment #5)
> > > > > (In reply to Chris Dumez from comment #4)
> > > > > > (In reply to Ahmad Saleem from comment #3)
> > > > > > > (In reply to Chris Dumez from comment #2)
> > > > > > > > (In reply to Chris Dumez from comment #1)
> > > > > > > > > https://jsfiddle.net/ts7ad8zp/show is already fully passing on trunk. The 2
> > > > > > > > > failures are not real failures, the exception name matches, only the
> > > > > > > > > exception string doesn't. We can choose whatever string/description we want
> > > > > > > > > for exceptions.
> > > > > > > > > 
> > > > > > > > > https://jsfiddle.net/pLahgb8q/show does have a few legit-looking failures
> > > > > > > > > though. Firefox and Chrome pass all the tests, we don't.
> > > > > > > > 
> > > > > > > > The weird thing though is I thought I had imported
> > > > > > > > https://jsfiddle.net/pLahgb8q/show as layout test as
> > > > > > > > LayoutTests/fast/forms/textarea-maxlength.html. However, we are passing all
> > > > > > > > the checks for this test.
> > > > > > > 
> > > > > > > I took updated copy of test from https://source.chromium.org/.
> > > > > > 
> > > > > > LayoutTests/fast/forms/textarea-maxlength.html is a straight copy of Blink's
> > > > > > web_tests/fast/forms/textarea/textarea-maxlength.html as far as I can tell.
> > > > > 
> > > > > You are right. I just did 'diffcheck' on both test and except 'Error String'
> > > > > and one comment, there is no difference in both.
> > > > > 
> > > > > Weird - if these tests are failing in JSFiddle but passing via Test Runner.
> > > > 
> > > > Indeed! Might be a behavior difference when running in a third-party iframe
> > > > (since that's how jsFiddle runs the test case).
> > > 
> > > Let me make local HTML and then run them on WebKit ToT local build.
> > 
> > Yes - it is JSFiddle playing around. Using local copy on WebKit ToT, we pass
> > all tests.
> 
> Looking at the test case, I bet this is a focus behavior difference. I
> suspect the JS is not able to focus the fields in the third-party iframe and
> thus we end up with empty fields.

Should we mark this as "RESOLVED INVALID" or rename title to something along the lines of 'focus' issue in third party iframes?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230305/5edc28a2/attachment-0001.htm>