Closed Bug 242507 Opened 20 years ago Closed 16 years ago

"Edit link in New Composer" puts cursor before body

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: boofy_bloke, Unassigned)

Details

(Whiteboard: [Make blinking caret always viewable]) 

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040428
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040428

In normal view the cursor is right at the top of the window and I have to arrow
right or down to get to the first text of the page.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
This depends on the page code actually. The caret is normally placed before the
first editable element inside the body node. Sometimes, the first element is an
image positioned in the body's left side margin or when the body has no margin.
Maybe you don't view the blinking caret because of this. But the caret should be
after the starting tag of the body node.


I checked again carefully the caret situation/problem your description refers to.

Copy and paste the following HTML code into a blank Composer page in HTML source
editing mode (between <body> and </body> tags):


<p>Instructions: right-click the following links and choose "Edit Link in New
Composer"<br>
</p>
<p><a href="http://www.mozilla.org/docs/web-developer/">Web developer
documentation</a> Case 1: Absolutely positioned &lt;img&gt; at upper top left of
document<br>
</p>
<p><a href="http://www.htmlhelp.org/">HTML Help from Web Design Group</a> Case
2: Non-positioned &lt;img&gt; at upper top left of document<br>
</p>
<p><a href="http://diveintoaccessibility.org/table_of_contents.html">Dive Into
Accessibility</a> Case 3: Page starts with text "Dive into..." but there is the
abs. pos. div "You are here" which overlaps<br>
</p>
<p><a href="http://maccaws.org/">Making a Commercial Case for Adopting Web
Standards</a> Case 4: Page starts with text and has no abs. pos. element<br>
</p>


The blinking caret is always positioned at the first replacable or editable
element in the body node (in Normal and HTML Tags editing modes). Now, there are
cases where you won't be able to see (or see clearly) the blinking caret:
- an absolutely positioned element (an <img> or <div>, say, positioned at top:
0px; and left: 0px;) will overlap over (therefore mask) that first editable or
replacable element. This is case 1 and case 3 in the provided chunk of code/testcase
- If body margins are modified and set to 0, then that could affect the way
Composer would render (and position initially) the blinking caret in the freshly
opened Composer window. This is the case for maccaws.org (case 4) (the blinking
caret is barely viewable or partially clipped) in which the file
http://maccaws.org/includes/layout.css
uses the CSS declaration body {margin: 0;}

Maybe the real issue here should be to make the blinking caret always visible,
entirely viewable regardless of these abs. pos. and margin situations in HTML
Tags editing mode.

Mozilla 1.8a3 build 2004080509 here.
Whiteboard: [Make blinking caret always viewable]
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

With the following text, the cursor is put before the SSI code. When I remove
that, the cursor appears befor the first editable text (i.e. 9 surveillance
images...)

<body>
<!--#include virtual="../../ssi/header.shtml" -->
<h6 class="top"><a href="#images">9 surveillance images are loading at
the bottom of the page</a><a name="top"></a></h6>
Matti, is this still a valid bug? Please, test this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.