Closed
Bug 4524
Opened 26 years ago
Closed 26 years ago
text frame painting errors when moving text content
Categories
(Core :: Layout, defect, P2)
Tracking
()
VERIFIED
FIXED
M5
People
(Reporter: buster, Assigned: buster)
References
()
Details
run apprunner -editor
in test page, select "next paragraph is a block"
make bold (Ctrl-B)
this causes the text node containing the selection to get wrapped in a "B" span.
notice that the text doesn't repaint unless you cause a reflow (but don't do
this yet.)
right arrow. notice how poorly the line paints. once you've arrowed over all
the text, the line has painted correctly.
Severity: normal → critical
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M4
Well, I can't reproduce this: (1) it renders correctly the first time for me.
(2) the arrow keys (on linux) work exactly once. The second key (either
direction) does nothing.
Back to you steve...
The OS is set to NT. It still happens on NT as of debug built from code at
4:00pm today. I see this on 2 different machines (work and home, both NT) Back
to you...
This might be a dup of 4593. Kipp and Mike should talk and come up with a
strategy for attacking this problem so they don't duplicate effort. In private
messages, Kipp has indicated that this doesn't happen on Linux, and probably
isn't a general text update problem. Selection is the next most likely culprit.
adding test case, because the editor test page has changed.
<html>
<head>
<title>Ender Startup Page</title>
</head>
<body bgcolor="#FFFFFF" text="#000000">
<h1>Welcome to the Gecko Editor Test Bed</h1>
<P>This next paragraph is a blockquote.</P>
<BLOCKQUOTE type="cite">
Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do eiusmod tempor
incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis
nostrud exercitation
ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor
in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat
cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est
laborum Et harumd und lookum like Greek to me, dereud facilis est er expedit
distinct. Nam liber te
conscient to factor tum poen legum odioque civiuda. Et tam neque pecun modut est
neque nonor et imper ned libidig met, consectetur adipiscing elit, sed ut labore
et dolore magna
aliquam makes one wonder who would ever read this stuff? Bis nostrud
exercitation ullam mmodo consequet. Duis aute in voluptate velit esse cillum
dolore eu fugiat nulla pariatur. At
vver eos et accusam dignissum qui blandit est praesent luptatum delenit aigue
excepteur sint occae. Et harumd dereud facilis est er expedit distinct. Nam libe
soluta nobis eligent optio
est congue nihil impedit doming id Lorem ipsum dolor sit amet, consectetur
adipiscing elit, set eiusmod tempor incidunt et labore et dolore magna aliquam.
Ut enim ad minim veniam,
quis nostrud exerc. Irure dolor in reprehend incididunt ut labore et dolore
magna aliqua.
</BLOCKQUOTE>
<P>
Lorem ipsum is latin, slightly jumbled, the remnants of a passage from Cicero's
_de Finibus_ 1.10.32, which begins 'Neque porro quisquam est qui dolorem ipsum
quia dolor sit
amet, consectetur, adipisci velit...' [There is no one who loves pain itself,
who seeks after it and wants to have it, simply because it is pain.]. [de
Finibus Bonorum et Malorum,
written in 45 BC, is a treatise on the theory of ethics very popular in the
Renaisance.]
</P>
<P>
"What I find remarkable is that this text has been the industry's standard dummy
text ever since some printed in the 1500s took a galley of type and scambled it
to make a type
specemin book; it has survived not only four centuries of letter-by-letter
resetting but even the leap into electronic typesetting, essentially unchanged
except for an occational 'ing' or
'y' thrown in. It's ironic that when the then-understood Latin was scrambled, it
became as incomprehensible as Greek; the phrase 'it's Greek to me' and
'greeking' have common
semantic roots!"
</P>
</body>
</html>
with code from 4/20 late afternoon, I no longer see this problem.
apprunner was not necessary for this bug, it was also possible to recreate this
bug using the test case in viewer.
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 8•26 years ago
|
||
Fixed in April 23rd Build.
You need to log in
before you can comment on or make changes to this bug.
Description
•