WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
UNCONFIRMED
19687
WebFrameView does not respond to setAllowsScrolling:YES but does respond to setAllowsScrolling:NO
https://bugs.webkit.org/show_bug.cgi?id=19687
Summary
WebFrameView does not respond to setAllowsScrolling:YES but does respond to s...
Tom Lynch
Reported
2008-06-20 00:33:00 PDT
As above WebFrameView does not respond to setAllowsScrolling:YES however it does respond to NO... To test this I have written a small application in xcode, however you will need to be running the very latest iPhone SDK build of xcode to actually use the project file, but you can see the AppContoller and build your own test, I also included the log where you can see that the result of allowsScrolling does change from 1 to 0 but never changes back. After discussion with irc.freenode.net #macdev we feel that this is one of two possibilities either bad documentation and that it has to be done in a different way, or a bug. I and the others tend to feel the latter is true.
Attachments
Add attachment
proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1
2009-10-01 15:53:13 PDT
<
rdar://problem/7269555
>
Tom Lynch
Comment 2
2009-10-01 16:14:23 PDT
This has been tested with the latest Safari Version installed on 10.6 4.0.3 (6531.9) and it still does not work.
Daniel Bates
Comment 3
2009-10-06 22:58:58 PDT
Where is the log? (In reply to
comment #0
)
> As above WebFrameView does not respond to setAllowsScrolling:YES however it > does respond to NO... > > To test this I have written a small application in xcode, however you will need > to be running the very latest iPhone SDK build of xcode to actually use the > project file, but you can see the AppContoller and build your own test, I also > included the log where you can see that the result of allowsScrolling does > change from 1 to 0 but never changes back. > > After discussion with irc.freenode.net #macdev we feel that this is one of two > possibilities either bad documentation and that it has to be done in a > different way, or a bug. I and the others tend to feel the latter is true.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug