WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
27707
[WML] History handling / page cache / loading is buggy and depends on several hacks
https://bugs.webkit.org/show_bug.cgi?id=27707
Summary
[WML] History handling / page cache / loading is buggy and depends on several...
Nikolas Zimmermann
Reported
2009-07-27 05:08:19 PDT
As the summary says the whole WML loading / page cache / history handling is flawed. It depends on several hacks in FrameLoader / WMLGoElement / WMLCardElement / WMLPageState. * There should be no need to track the history length on our own * <go> / <a> / <anchor> / <do> / <prev> shouldn't need to deal with the FrameLoader directly (currently setting setForceReloadWmlDeck() * FrameLoader needs to detect WML documents and handle them approriate (always reload, no caching, etc.) The tricky part is detecting our layout tests which embed WML content in a XHTML document (which is really 'hacky', but needed for our automatic testing facilities). Fixing these issues should stabilize the loading area between running the layout tests standalone in DRT and using WML docs directly. Uploading a patch with new testcases soon.
Attachments
Initial patch
(24.68 KB, patch)
2009-07-27 09:46 PDT
,
Nikolas Zimmermann
staikos
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Nikolas Zimmermann
Comment 1
2009-07-27 09:46:27 PDT
Created
attachment 33553
[details]
Initial patch
Nikolas Zimmermann
Comment 2
2009-07-27 10:04:53 PDT
Landed in
r46418
.
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