Bug 121665 - [testcase] Unable to change encoding for specific or all frames
Summary: [testcase] Unable to change encoding for specific or all frames
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-09 20:15 UTC by Tal Levy
Modified: 2008-04-17 10:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
index.htm (116 bytes, text/html)
2008-04-07 02:00 UTC, Christophe Marin
Details
frame1.htm (726 bytes, text/html)
2008-04-07 02:01 UTC, Christophe Marin
Details
frame2.htm (726 bytes, text/html)
2008-04-07 02:01 UTC, Christophe Marin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tal Levy 2006-02-09 20:15:36 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Unlisted Binary Package

When changing the encoding on a page with frames, only the main biggest frame seems to change while any side frames keep their encoding.  Right clicking a frame does show an expandable submenu "Frame", so either that submenu should contain an encoding option, or setting the page encoding should set all frames' encoding.
This bug occurs on a page that uses javascript (a bank account page) but I am not sure if this is a khtml or kjs bug.
Comment 1 Christophe Marin 2008-04-07 02:00:14 UTC
Created attachment 24254 [details]
index.htm
Comment 2 Christophe Marin 2008-04-07 02:01:14 UTC
Created attachment 24255 [details]
frame1.htm
Comment 3 Christophe Marin 2008-04-07 02:01:41 UTC
Created attachment 24256 [details]
frame2.htm
Comment 4 Christophe Marin 2008-04-07 02:01:49 UTC
The issue is resolved in konq4 (SVN. 793966). 

Adding 3 files for this report. index.htm and frame1.htm / frame2.htm.

Users can change each frame encoding then globally revert/change the page encoding in the view menu.

Comment 5 George Goldberg 2008-04-17 10:55:47 UTC
Using test-case in comment #4, this bug seems to be fixed in 3.5.9 and trunk.