Omitting link tag with id of "bespin_base" and href pointing to the base of bespin files causes loading to fail

RESOLVED FIXED in 0.9

Status

Skywriter
General
--
blocker
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: Andrew Petersen, Assigned: Kevin Dangoor)

Tracking

unspecified
x86
Windows XP

Details

(URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: 0.8.0 Drop-In 

Having a link tag of <link id="bespin_base" href="./bespin-0.8.0">, is required. My directory structure is as follows (test being a folder being served by apache somewhere, not the web root):

test/bespin.0.8.0/
test/testpage.html

If I view testpage.html in a browser, served by local xampp (url
something like: http://localhost/dev/other/folders/here/test/testpage.html),
and do not specify that link tag, nothing happens, no errors, and
bespin does not load. The window.onBespinLoad callback never fires
either.

bespin_base also isn't mentioned anywhere in the docs.

Reproducible: Always

Steps to Reproduce:
1. Remove or put the wrong path to bespin as the value of the href attribute of a link tag with an id of bespin_base
2. Notice that bespin does not load, and no errors appear in console.
Actual Results:  
Notice that bespin does not load, and no errors appear in console.

Expected Results:  
Bespin loads, and fires the onBespinLoad callback.

The URL of this bug is pointing to a zip file containing two html files that reproduce this issue. One file works, the other is broken.
(Assignee)

Comment 1

8 years ago
targeting 0.8.1 to create a fix for this.
Target Milestone: --- → 0.8.1
(Assignee)

Updated

8 years ago
Assignee: nobody → kdangoor
Severity: normal → blocker
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: 0.8.1 → 0.9
(Assignee)

Comment 2

8 years ago
documentation updated to reflect the need for the <link> tag in 68f3bf2d6372
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.