[Webkit-unassigned] [Bug 57604] Remove nonstandard noresize attribute from HTML FrameSet Element

Thu Jun 23 09:50:27 PDT 2011

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

--- Comment #28 from Darin Adler <darin at apple.com>  2011-06-23 09:50:27 PST ---
(In reply to comment #27)
> 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.

Generally speaking, I don’t think the documentation tells us one way or another what the effect will be.

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

There’s no simple answer. There has to be a risk/benefit consideration.

In some cases we take a risk and change behavior. The Apple Safari and WebKit team then has to deal with fallout later, diagnosing problems, tracking them down and figuring out which behavior change led to the symptom. Doing this diagnosis can be quite costly and frustrating, but risking it can be worth it if there is significant cost to keeping the legacy behavior.

Sometimes we end up adding a quirk to keep an old version of the application or website working while giving a path forward for others and newer versions.

In other cases, we keep some a legacy feature, such as a WebKit variant of some standardized feature, in the software long term. While this might frustrate some working on the project who get no benefit from keeping the legacy version of the feature, the cost is often low and bearable.

There may be others working on the project who have more perspective on this.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.