IE11:
(default)
document.body.tabIndex = 0
document.head.tabIndex = 0
document.documentElement.tabIndex = 0
document.body.focus() -> work (regardless of tabIndex)
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>JS Bin</title> | |
</head> | |
<body> | |
<div id="yosin"> | |
<span class=name>Yoshifumi</span> |
<link rel="import" href="../paper-button/paper-button.html"> | |
<link rel="import" href="../paper-checkbox/paper-checkbox.html"> | |
<link rel="import" href="../core-animated-pages/core-animated-pages.html"> | |
<link rel="import" href="../core-animated-pages/transitions/hero-transition.html"> | |
<link rel="import" href="../core-animated-pages/transitions/cross-fade.html"> | |
<link rel="import" href="../core-animated-pages/transitions/slide-down.html"> | |
<link rel="import" href="../core-animated-pages/transitions/slide-up.html"> | |
<link rel="import" href="../core-animated-pages/transitions/tile-cascade.html"> | |
<link rel="import" href="../paper-input/paper-input.html"> | |
<link rel="import" href="../google-map/google-map.html"> |
@keyframes rect { | |
0% { width: 20px; height: 100px; } | |
100% { width: 100px; height: 20px; | |
border-radius: 10px; } | |
} | |
div#rect { | |
position: absolute; | |
top: 20px; | |
left: 100px; |
#include <iostream> | |
int add1(int x) { | |
return ++x; | |
} | |
int double2(int x) { | |
return 2 * x; | |
} |
wtf/Assertions.h
has BACKTRACE()
, but it seems to fail to decode some symbols.
Chromium's base/debug/stack_trace.h
works better at least on Linux. One caveat is
that unless explicitly add base.gyp:base
in core.gyp
, link fails on
component=shared_library
(GYP) build.
printf()
is usable in Blink, but fprintf(stderr, ...)
looks better if used with backtrace.
This document describes how custom elements v1 work when they are defined or used in HTML Imports.
HTML Imports is currently implemented only in Chrome, and this document provides non-normative information about Chrome's implementation in M54 and later, for the reference of future works that tries to achieve similar functionality like HTML Imports.
As the global context window
is shared with script running in an imported document, you can access the custom elements registry via window.customElements
. This is straightforward and no different from the usage in a usual HTML document.
<!DOCTYPE html> | |
<body> | |
<div id="root"></div> | |
</body> | |
<script> | |
'use strict'; | |
if (window.testRunner) { | |
testRunner.dumpAsText(); | |
} |
<!DOCTYPE html> | |
<body> | |
<div id="root"></div> | |
</body> | |
<script> | |
'use strict'; | |
if (window.testRunner) { | |
testRunner.dumpAsText(); | |
} |
<!DOCTYPE html> | |
<body> | |
<div id="root"></div> | |
</body> | |
<script> | |
'use strict'; | |
if (window.testRunner) { | |
testRunner.dumpAsText(); | |
} |