-----BEGIN PGP SIGNED MESSAGE-----
What if a title’s HREF is pointing to a different page? Nothing.
There won’t be any problems, UI-wise or HREF link-wise.
The # at the end of the URL is called a “fragment” (see perldoc URI).
The fragment is essentially ignored in retrieving content from URLs by
web browsers. It’s only really used to short-cut navigation to a
particular part of the page further down, after the first page
"break". So I’m not modifying what url the HREF is point to at all.
If there happens to be a titlebox on the linked to page, then the
patch takes care of the destination . If not, then everything
is still OK because the # and everything past it is ignored.
For example (my patch applied):
This works because the destination exists, because there’s a
TitleBox with the same title in the Edit.html page.
This doesn’t, because there isn’t a TitleBox on in the Advanced.html
page named “Articles”. But that’s ok, because the browser ignores a
link to an that doesn’t exist.
Does this answer your question? If there’s a better way to do this,
I’m open to suggestions.On 09/08/09 19:49, Ruslan Zakirov wrote:
What if title’s href is pointing to a different page?
On Tue, Sep 8, 2009 at 7:25 PM, Richard Harmanrtemail@example.com wrote:
At my office I extended my RT UI by adding four more TitleBox widgets,
to hold custom fields specific to what my office does. In order to
speed up accessibility, I modified the TitleBoxStart component to
include an tag, and modify the TitleBox’s title to point to the
This lets people jump down to the part of the edit page they’re focused
on directly, instead of having to scroll down.
“Looks like there’ll be no money for you, Crazy Round Man.”
- Samurai Jack
Richard G Harman Jr firstname.lastname@example.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----