I'm confused about whether onFocus/onBlur events should bubble in preact, like they do in React.

In this example using preact 10.0.0-beta.1 they don't bubble https://codesandbox.io/embed/5wxk9zk7lx

...whereas in the Preact repl they do bubble https://preactjs.com/repl

export default () =>(
  <div onFocus={() => console.log("FOCUS")}>
    <div>
      Focus this input
   

• html2canvas version tested with: ^1.0.0-rc.5
• Browser & version:ios10
• Operating system:ios
  html2canvas(document.body,{
  type:'view',
  'user-select':'auto',
  useCORS:true,
  async: true
  }).then(canvas => {

Marko Version: 4.18.4

Details

I use some facebook markup that I let facebook parse from DOM:

      <fb:login-button 
        auto-logout-link="false"
        button-type="continue_with" 
        size="large"
        scope="public_profile,email" 
        use-continue-as="true">
      </fb:login-button>

In my onMount I then let the facebook API do it's thing with th

Many methods that allows instreams as parameter exposes infos about closing the stream. Example:
Properties#load:

• The specified stream remains open after this method returns.

This information is very usefull. I miss that in Jsoup.parse();

After intensive inspection of the sourcecode I was able to find out that the instream is not closed. To avoid this inspection-work the documentation sh

when i import this file in .vue, there are many wrong because of eslint.
when i use it through script, the browser got ZeroClipbard is not defined....

Expected behavior

In the Choo docs on Routing, in the section "Listening for Route Changes" implementing:

var html = require('choo/html')
var choo = require('choo')
var app = choo()

var app = choo()
app.use((state, emitter) => {            // 1.
  emitter.on('navigate', (route) => {    // 2.
    console.log(`Navigated to ${route}`) // 3.
  })
})

Should return a conso

Use case: description, code

jsfiddle example

Expected behavior

Dont parse '%22', when inside a attribute

Actual behavior (stack traces, console logs etc)

Parses '%22' as a '"', which causes a parsing error.

Library version

Newest

Browsers

• Chrome 49+
• Firefox 45+

Small rant sorry...

You should mention somewhere that elements have to be hidden first then do ramjet.transform(), and use { done: => { ramjet.show(target) }}... and also maybe that it doesnt like jquery elements.

If the docs do say that, my apologies, I couldn't find it

Reason is all your demos use hidden elements, but its not clear how to interact with a hidden element, and the effect doe

We should have a documentation website, perhaps generated from our readme or the other way around, in order to make it easier for people to learn about Cash and browse its functionalities.

If anybody would like to spend the time to make it it'd be awesome.

Description

Right now there is no documentation on how to run tests for this repository, It would be great if a simple document/ section of the readme could outline how to run the tests locally

Why

this would make it faster for people to dig into the compiler and understand it by observing the effects their changes have on tests. It would also support good, tested contributions by ma

The v1 release is coming closing (as is the v0.10; the last milestone before v1), which means a full documentation will be required.

This has a lot of impact:

• Move parts of the Wiki to the docs
• Create a common documentation infrastructure (common means: good for all AngleSharp projects)
  • Format of the documentation (potentially markdown with many extensions)
  • Special diagram lan

@foolip Philip,

I presume you are one of the wpt maintainers.
Is the svg flag valid or deprecated?
<meta content="svg" name="flags">
I have declared the svg flag in 2 tests
and in 2 reference files so far:
web-platform-tests/wpt#20033
web-platform-tests/wpt#21450
svg is not in the list of valid flags
http://web-platform-tests.or

I only tried the image zoom and splitter demos, but neither of these work on mobile, and probably won't work on tablets.

The whole project likely needs testing and optimization for touch input?

In many cases, this isn't going to be simple or elegant and will likely increase the complexity of some of these demos substantially, which might be harmful to the learning process for some, so there

General Information

• [+ ] Improvement
• [+ ] Feature

Description

It may be useful: High-quality C++ HTML parser from cobalt.foo project. CMake port of it can be found at https://github.com/blockspacer/skia-opengl-emscripten/issues/5 and https://github.com/blockspacer/skia-opengl-emscripten/blob/master/src/cobalt/cobalt_dom.cmake#L32

Some possible use cases:

• Create some

The navigation in the documentation is currently showing a horizontal scrollbar and isn't full-height.

I'm not sure if it's supposed to be full-height, but I think the horizontal scrollbar should be an easy fix by just making it slightly wider ;)

Here's a screenshot to show what I mean:
![capture](https://cloud.githubusercontent.com/assets/152227/14913804/d8c2c74c-0e05-11e6-92f5-3e2d97904e92.PNG

https://github.com/GoogleChrome/puppeteer/blob/v1.11.0/docs/api.md#class-coverage

Coverage gathers information about parts of JavaScript and CSS that were used by the page.

An example of using JavaScript and CSS coverage to get percentage of initially executed code:

// Enable both JavaScript and CSS coverage
await Promise.all([
  page.coverage.startJSCoverage(),
  page.coverage.

It would be great to have documented the babel configuration to use the transform-class-properties plugin on Can 6 documentation to export classes with static properties using steal.

If we don't use the configuration an error like this will be displayed when I execute steal-tools export:

{ SyntaxError: unknown: Missing class properties transform.
   5 | 
   6 | export default class Fa

Describe the feature you'd like:

Being new to testing-library, it all is a bit overwhelming. The long list of matchers jest-dom introduces, also makes it harder to start out.

Suggested implementation:

Group the matchers in the documentation over some headings, e.g. “Checking element existence”, “Checking forms”, “Checking element state”.

Describe alternatives you've cons

Let’s say you accidentally add find: ‘.’ or other invalid values. Now it would throw and not clean up properly.

Checking should happen somewhere around here

A try/catch should do the trick I think. In the catch block the cleaning up could happen (calling h.stop could not work, so manual