Found it. Here is the source shows when posted:
<video width="640" height="480" controls="controls"><br />
<source src="http://files.animeget.org/HxH/HxH_01_HD.mp4" type="video/mp4"><br />
</video>
However, if you turn it into a MyCode, it should work without any problems and you don't leave your forum as exposed to security holes when allowing HTML. At least in the Admin CP it works. Posting still returns the same problem, if HTML is turned on.
Expression:
\[video=(.*?)\](.*?)\[/video\]
Source:
<video width="640" height="480" controls="controls">
<source src="$2.$1" type="video/$1">
</video>
Because the <source> tag is being caught by the HTML filter to replace <script> and <style> tags, I can see that it could possibly look like a bug when posting with HTML instead of MyCode. However before HTML5, it worked as intended. So a staff will have to decide whether it really is a bug or it is working as intended considering HTML5 is fairly new, at least compared to 1.6. This might get fixed in 1.8 since it is gearing up for release (already public beta version 1).
Here is the filter, located in
inc/class_parser.php starting on line 112 (roughly):
if($this->options['allow_html'] != 1)
{
$message = $this->parse_html($message);
}
else
{
while(preg_match("#<s(cript|tyle)(.*)>(.*)</s(cript|tyle)(.*)>#is", $message))
{
$message = preg_replace("#<s(cript|tyle)(.*)>(.*)</s(cript|tyle)(.*)>#is", "<s$1$2>$3</s$4$5>", $message);
}
$find = array('<?php', '<!--', '-->', '?>', "<br />\n", "<br>\n");
$replace = array('<?php', '<!--', '-->', '?>', "\n", "\n");
$message = str_replace($find, $replace, $message);
}