Closed
Bug 288387
Opened 19 years ago
Closed 18 years ago
Composer: Ctrl+Home shows <#document> <html> in the status bar
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: boofy_bloke, Unassigned)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
159 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050326 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050326 When I open a page at my sight the cursor is at the top of the table and the status bar says: <body>. Ctrl+Home moves the cursor to the top right of the page (almost off-screen) and the status bar says: <#document> <html>. Reproducible: Always
Comment 1•19 years ago
|
||
can you attach an html document that exhibits this behavoir (preferably the minimal needed to reproduce the bug)?
Version: Other Branch → Trunk
http://thecia.com.au/index.shtml or any other page at the site.
Comment 3•19 years ago
|
||
after loading this html in composer, hitting ctrl-home triggers the bug as Matti described. A new document in composer does not have this problem, but if you save it and then reload, the bug appears.
Comment 4•19 years ago
|
||
Also, after hitting Ctrl-home, I get a lot of these: An error occurred updating the cmd_absPos command: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsICommandController.getCommandStateWithParams]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://editor/content/ComposerCommands.js :: goUpdateCommandState :: line 258" data: no] this regressed between linux trunk builds 2004112905 and 2004113006
Comment 5•18 years ago
|
||
Can you verify that this bug had been fixed? I'm not reading this problem with the latest build for Win2000. Thanks...
Comment 6•18 years ago
|
||
Yes, WFM as well with SeaMonkey 1.0.4 and current trunk.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•