cancel
Showing results for 
Search instead for 
Did you mean: 

DCX sub-topic links seem broken

Breck_Carter
Participant
1,743

The following DCX sub-topic link works fine from within the DCX Index tab; it correctly jumps to the COMPUTE clause section of the CREATE TABLE topic.

(...which, by the way, is A VERY COOL FEATURE)

However, when you try to use it from outside DCX (e.g., from the browser URL bar), it briefly flashes the COMPUTE clause section and then scrolls way down:

http://dcx.sybase.com/index.html#1201/en/dbreference/create-table-statement.html*d5e43904

Accepted Solutions (0)

Answers (1)

Answers (1)

MarkCulp
Participant
0 Kudos

This is a function of the browser, not DCX. I.e. the browser decides when to render the page and display the contents to the user. I suspect what is happening is that when DCX is already loaded the page contents are loaded faster than when the link is clicked externally from DCX. I.e. when clicked externally not only does the CREATE TABLE topic page need to be loaded but all of the other content required for DCX needs to be loaded (the top, left, bottom panels plus all of the underlying javascript and style sheets), and all of this causes the browser to behave differently.

Breck_Carter
Participant
0 Kudos

It's Bush's fault!

VolkerBarth
Contributor
0 Kudos

Would "#" anchor tags help to make sub-topics available? IMHO (which is surey limited!), they work reliable even when used with web sites whose pages have not been loaed.

For e.g. they work fine in this forum to link to answers, such as

http://sqlanywhere-forum.sap.com/questions/12027#12045

VolkerBarth
Contributor
0 Kudos

Sorry, such a dumb proposal, I had completely overseen the fact that in DCX links, a "#" symbol is already used to specify the version (or whatever)...see Breck's sample.

Breck_Carter
Participant
0 Kudos

@Mark: That's so cool! ...the developers of Chrome, Firefox and IE all got together to implement exactly the same wrong behavior:

First, scroll the topic page down to the subtopic and briefly display it (the correct result),

Then, having teased the user with the correct behavior, quickly scroll down to almost the bottom of the topic, but not quite the bottom, and leave the display there (worse than useless result).

Half the time those guys can't agree on W3 standards let alone code "the wrong way" the same way.

Oh, well, I coulda sworn it used to work, but I can't find proof... Bush deleted it 🙂