[Webkit-unassigned] [Bug 57604] Remove nonstandard noresize attribute from HTML FrameSet Element
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jun 23 03:04:20 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=57604
--- Comment #27 from Mustafizur Rahaman <mustaf.here at gmail.com> 2011-06-23 03:04:20 PST ---
(In reply to comment #25)
> (In reply to comment #23)
> > Regarding impact of these changes on other code, I have verified that this "noresize" attribute is only used for RenderFrameSet/RenderFrame (and that's why I did not modify anything in RenderFrame). Also, I have verified with a more complex test case of nested Frameset & Frames with various combination of "noresize" and found the behavior to be same as FF behavior.
>
> I said code, but I was unclear. I did not mean code inside WebKit. I meant things like Mac OS X applications, iOS applications, and Dashboard widgets depending on WebKit behavior. These are the categories I know about because of my work at Apple. There may be others as well.
>
Hi Darin,
I did some research on this, I have come across this link http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/Attributes.html which says "noresize" is used for frame tag. So, I was wondering whether any Apple implementation would use "noresize" for frameset.
Other than this, I did not come across any content on the net which uses "noresize" for frameset.
Please let me know whether based on this info, we can land this patch (then I will update another patch with incorporating your review comments). Else, we can mark this issue as invalid (with appropriate explanation).
On a side note, I have a question (because I am relatively newer in WebKit). In any such kind of fixes, if a legacy app depends on wrong WebKit behavior, then the app would break if we try to fix. Then what is the general philosophy/guideline we normally follow in such issues?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list