On 16.01.2013 16:03, Kim Haase wrote:
On Firefox 10 (sorry, old) and IE 8 the behavior seems to be the same
on both the 10.9.1 and 10.8.3 pages.
On Firefox the fact that there are apparently no line breaks for
punctuation at all means that the Description column has the width of
the longest "word" in the descriptions, which is
testBTreeForwardScan_fetchRows_resumeAfterWait_nonUnique_split(org.apache.derbyTesting.functionTests.tests.store.IndexSplitDeadlockTest)junit.framework.AssertionFailedError:
So I need to scroll the table horizontally to be able to read all the
descriptions.
IE 8, on the other hand, refuses to obey your instructions and breaks
after the hyphens anyway (and after some other punctuation marks). The
same long line appears in both the 10.9.1 and 10.8.3 release notes
because DERBY-5440 was fixed in both.
Thanks for testing this, Kim.
Are you sure you actually got the new version of the page?
I noticed that a proxy tried to fool me in the office. I observed that I
first got the page with the first attempt of a fix, and then after
having made the second change I got the original page (i.e without any
of my changes). At that point I was unable to get the newest version
(CTRL-R and F5 didn't help).
I see this now:
o Firefox behaves ok with both the old and the new version of the 10.8
page.
o Chrome improves with the changes on the 10.8 page (no breaking of
DERBY-XXXX).
o IE 9 improves with the changes on the 10.8 page (no breaking of
DERBY-XXXX).
--
Kristian
Kim
On 01/16/13 09:02 AM, Kristian Waagan wrote:
Hello,
FYI, I'm testing a table formatting fix on the 10.8.3.0 download
page. From the commit message:
------------------------------------------------------------------------
r846837 | kristwaa | 2013-01-16 14:38:13 +0100 (Wed, 16 Jan 2013) | 7
lines
Testing table formatting fix.
The problem is that some browsers, for instance Chrome, breaks
"DERBY-XXXX"
at the hyphen to try to accommodate the longest issue descriptions in
the
table of fixed issues.
On my system this happens even with a resolution of 1600x900, and it
makes the
table much harder to read.
------------------------------------------------------------------------
Now, that caused some issues when deployed, so I've tried another
approach in rev 846838.
I'd appreciate if you let me know if the fix is causing problems for
anyone. You can check how the download page for 10.8.3 compares to
for instance 10.9 to see if the change affected your browser.
If I don't hear anything I plan to incorporate the fix, or another
one that works better, in the ReleaseNotesGenerator.
I also have to verify that Forrest doesn't mess up the fix.
Thanks,
