Project

General

Profile

Actions

Support #1156

closed

LINK tag

Added by Anonymous about 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Pieter Libin
Target version:
Start date:
02/05/2012
Due date:
% Done:

0%

Estimated time:

Description

The class WApplication has some methods add META tags and stylesheets to the

section, but I did not find any information about adding LINK tags (of course, with the exception of stylesheets). But the html standard specifies lots of other values for the REL attribute:

http://www.w3.org/TR/html5/links.html#linkTypes

How can I - for example - add a to my Wt site?

Thanks in advance.


Files

hello.C (804 Bytes) hello.C Pieter Libin, 02/15/2012 01:39 PM
Actions #1

Updated by Koen Deforche about 12 years ago

  • Status changed from New to InProgress
  • Assignee set to Pieter Libin

Pieter,

We should add API for this, which is simular to the addMetaHeader() removeMetaHeader() and rendered in the same way (only with progressive bootstrap mode).

Regards,

koen

Actions #2

Updated by Kurt Roeckx about 12 years ago

I was just looking for the same thing.

Koen Deforche wrote:

Pieter,

We should add API for this, which is simular to the addMetaHeader() removeMetaHeader() and rendered in the same way (only with progressive bootstrap mode).

I don't get the comment about the progressive bootstrap mode. I would like to have them always show up.

Kurt

Actions #3

Updated by Pieter Libin about 12 years ago

Add code that tests all supported links

Actions #4

Updated by Pieter Libin about 12 years ago

  • Status changed from InProgress to Resolved
  • Target version set to 3.2.1

Hey Kurt,

Since the browser ignores most of the elements set through DOM

manipulation, and most of them only make sense for meta-search engines

anyway (who do not understand/execute JavaScript), it does not make

much sense to set it with javascript.

The only 2 ways were wt sends an HTML page containing these link elements is:

  • when using wt in plain html mode
  • when using progressive bootstrap Wt will initially assume that the user agent is a plain HTML user-agent and immediately create the application and send an initial response that will contain the initial page suitable for a plain HTML user-agent (containing the link elements in the head of the page). JavaScript embedded in this page will sense for Ajax support and trigger a second request which progresses the application to an Ajax application.

Kind regards,

Pieter

Actions #5

Updated by Kurt Roeckx about 12 years ago

Pieter Libin wrote:

Hey Kurt,

Since the browser ignores most of the elements set through DOM

manipulation, and most of them only make sense for meta-search engines

anyway (who do not understand/execute JavaScript), it does not make

much sense to set it with javascript.

I known browsers that do use it, but I don't know about after DOM manipulation. I would argue that it would be a bug in the browser if they don't properly support it then anymore, and that that is no good reason not implement it.

But I would be happy to start with the plain html mode.

Kurt

Actions #6

Updated by Wim Dumon about 12 years ago

Hello Kurt,

Can you tell us what you intend to do with the LINK tags? Maybe there's an interesting use case there to support in Wt.

Wim.

Actions #7

Updated by Kurt Roeckx about 12 years ago

Wim Dumon wrote:

Hello Kurt,

Can you tell us what you intend to do with the LINK tags? Maybe there's an interesting use case there to support in Wt.

I have a list of items and it's longer than 1 page. What I want to do is being able to indicate what the previous, next and first page is.

My main interest for this is currently for robots.

But browser can also use this to navigate to the next page. Which might not work well with WT since it wouldn't get the normal signal.

Kurt

Actions #8

Updated by Koen Deforche almost 12 years ago

  • Status changed from Resolved to Closed

Fixed in 3.2.1

Actions

Also available in: Atom PDF