Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Crash while updating TOC with hyperlinks (document specific) | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | jwernerny <flybrick> | ||||
Component: | code | Assignee: | stefan.baltzer | ||||
Status: | CLOSED DUPLICATE | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | OOo 1.0.1 | ||||||
Target Milestone: | --- | ||||||
Hardware: | Other | ||||||
OS: | Windows 98 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
jwernerny
2002-09-21 05:18:40 UTC
Hi, could you please check whether the file mentioned is still available - I couldn't load it. Or even better attach it to this issue using the "Create a new attachment" link above. Created attachment 3772 [details]
Zip of problem file and linked in graphics, etc.
I've uploaded the latest version of the file and all of the included documents / graphics. In the zip file, you will want "Framed Version started 21-Aug-02.sxw". Steps to duplicate issue: 1. Open Document (this may take a while because there are web based graphics also loaded) 2. On left side frame, under "Table of Contents", insert an "index / table of contents" 3. For the new TOC, add hyperlinks around the "E" and page number. 4. Click Okay 5. Watch it crash. This has crashed in 1.0.1 and 643. I have not yet tried it in 643C. The TOC you see there was manually created. [I may open another issue having to do with some hyperlinks or anchors not exporting correctly This makes my manual TOC not work work in the html version (index.html). I'll check in 643C first.] . *** This issue has been marked as a duplicate of 9446 *** As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. |