[Webkit-unassigned] [Bug 61558] iframe with scrolling=no incorrectly autoscrollable

[bugzilla-daemon at webkit.org]

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


Mustafizur Rahaman <mustaf.here at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darin at apple.com,
                   |                            |mustaf.here at gmail.com,
                   |                            |sarap.karthik at gmail.com




--- Comment #1 from Mustafizur Rahaman <mustaf.here at gmail.com>  2011-06-13 08:44:50 PST ---
As per discussion in webkit mailing list, I started the discussion 

Hi,

As per w3cschools (http://www.w3schools.com/tags/att_iframe_scrolling.asp ), the scrolling attribute of an iFrame element is expected to behave as per following
Attribute Values
Value     Description
auto     Scrollbars appear if needed (this is default)
yes     Scrollbars are always shown (even if they are not needed)
no     Scrollbars are never shown (even if they are needed)

My question is: When scrolling="no" & still if scroll bar is needed (i.e. if the content is larger than the iframe.), what would happen if i drag the content inside the iFrame? Will the iFrame content be scrolled OR would it not allow the user to scroll?

(https://lists.webkit.org/pipermail/webkit-dev/2011-June/017069.html)

-------------------------------------------
Antonio Gomes replied 

What does happen on other browsers? I know firefox does not scroll it (just tested), but maybe Opera and IE are good to be tested too.

Particularly speaking, I do not think it should scroll. Btw, it is a similar case to if user uses the find-in-page feature, and the word is offscreen the scrolling=no iframe. But it is a valid discussion, I think ...

(https://lists.webkit.org/pipermail/webkit-dev/2011-June/017071.html)

---------------------------------------------
Then Darin commented

HTML5 defines this scrolling attribute. It defines it in terms of a CSS overflow property on the frame below. The value scrolling="no" turns into overflow: hidden. Such overflow areas should not be scrolled.

As I understand it, generally speaking, if we have something like a find feature or autoscrolling code that scrolls outside the normal mechanism, it still should not scroll such an area and needs some other way to deal with content that is hidden by being off the edge of a scrollable area. This can happen with things like large margin values (particularly negative ones) as well as simply overflowing the space provided.

(https://lists.webkit.org/pipermail/webkit-dev/2011-June/017072.html)

Let's have the further discussion be continued here

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