[[html]] and [[embed]] unification
nav_first.pngFirst: thread:131
HTML Block
Edited: 11 Oct 2012 12:06 by: James Kanjo
Comments: 0
Tags:
nav_prev.pngPrevious: thread:324
Per-category feature: poll
Edited: 07 Mar 2010 06:18 by: leiger
Comments: 0
Tags:
Last: thread:112
Image Module
Edited: 12 Nov 2009 12:22 by: pieterh
Comments: 0
Tags:
nav_last.png
Next: thread:320
Previous discussions
Edited: 03 Mar 2010 22:54 by: leiger
Comments: 0
Tags:
nav_next.png

michal frackowiakmichal frackowiak wrote on 04 Mar 2010 09:40

The problem is that having both [[html]] and [[embed]], with really similar functionality and only subtle differences (at least from the user point of view), might not be necessary.

Many HTML embed scripts need to be placed directly in the page, and cannot be iframed. YouTube player works great, but if you try e.g. a TweetMeme retweet button, it will not work, because it cannot access URL of the original page. Instead it is fooled by the iframe.

So there are a few snippets (embeds) that we can trust, and they can be placed inline, in the page. Fine. Those mostly are listed in the list of supported embeds. But most of other embeds work fine in [[html]].

So what we can do is:

  • [[html]] = [[embed]] (in the implementation)
  • [[html]] places the snippet directly in the code for trusted (recognized) patterns
  • [[html]] iframes all other snippets

This should be all transparent to the user, without a need to understand the subtle differences in [[html]] and [[embed]], and it just works in most cases.


Start a new sub-thread

We discourage direct comments on this thread: to discuss it, please start a sub-thread.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License