|
1 | 1 | # Scala DOM Types
|
2 |
| -[](https://circleci.com/gh/raquo/Airstream) |
| 2 | +[](https://circleci.com/gh/raquo/scala-dom-types) |
3 | 3 | 
|
4 | 4 |
|
5 | 5 | _Scala DOM Types_ provides listings of Javascript HTML and SVG tags as well as their attributes, DOM properties, and CSS styles, including the corresponding type information.
|
6 | 6 |
|
7 |
| - "com.raquo" %%% "domtypes" % "<version>" // Scala.js 1.7.1+ |
8 |
| - "com.raquo" %% "domtypes" % "<version>" // JVM |
| 7 | + "com.raquo" %% "domtypes" % "<version>" // JVM & SBT |
| 8 | + "com.raquo" %%% "domtypes" % "<version>" // Scala.js 1.9.0+ |
9 | 9 |
|
10 | 10 | _Scala DOM Types_ is used by the following Scala.js UI libraries:
|
11 | 11 |
|
@@ -40,20 +40,20 @@ As well as by:
|
40 | 40 |
|
41 | 41 | ## Community
|
42 | 42 |
|
43 |
| -Please use [Github issues](https://github.com/raquo/scala-dom-types/issues) for bugs, feature requests, as well as all kinds of discussions, including questions on usage and integrations. You can _watch_ this project on github to get issue updates if you're interested in following discussions. |
| 43 | +Please use [Github issues](https://github.com/raquo/scala-dom-types/issues) for bugs, feature requests, as well as all kinds of discussions, including questions on usage and integrations. You can _watch_ this project on Github to get issue updates if you're interested in following discussions. |
44 | 44 |
|
45 | 45 |
|
46 | 46 | ## Contributing
|
47 | 47 |
|
48 | 48 | **Q: I want to add an element tag / attribute / prop / etc.**
|
49 | 49 |
|
50 |
| -**A:** Awesome! Please open an issue, and we will either add it, ask you to PR it, or explain why adding this particular key might not be a good idea. |
| 50 | +**A:** Awesome! Please open an issue, and we will either ask you to PR it, add it ourselves, or discuss why adding this particular key might not be a good idea. |
51 | 51 |
|
52 | 52 | So far we are focused on HTML5 attributes and read-writeable DOM props, but it doesn't have to stay that way. There is value in providing listings for popular non-standard attributes as well (e.g. `autoCapitalize`, `unSelectable`) but we haven't decided how to deal with those yet. Don't hesitate to trigger this discussion though.
|
53 | 53 |
|
54 | 54 | The raw definitions that you need to update are found in the [shared/main/.../defs](#TODO) folder. The sample code generated from those definitions is found in [js/test/.../defs](#TODO).
|
55 | 55 |
|
56 |
| -If making a PR, make sure to run the GeneratorSpec test locally, so that the sample generated code is updated before you commit. |
| 56 | +If making a PR, please make sure to run the `GeneratorSpec` test locally, so that the sample generated code is updated before you commit. |
57 | 57 |
|
58 | 58 |
|
59 | 59 | ## Why use _Scala DOM Types_
|
@@ -295,8 +295,8 @@ Here is what the DOM attributes / props / etc. are called in `scalaName`:
|
295 | 295 | * `content` prop is named `contentCss` to avoid using a common name
|
296 | 296 |
|
297 | 297 | #### Tags
|
298 |
| -* Scala tags names used to free up good names for end user code: |
299 |
| - * `style` -> `styleTag`, `link` -> `linkTag`, `param` -> `paramTag`, `map` -> `mapTag` |
| 298 | +* Scala tag names used to free up good names for end user code: |
| 299 | + * `style` -> `styleTag`, `link` -> `linkTag`, `param` -> `paramTag`, `map` -> `mapTag`, `dialog` -> `dialogTag` |
300 | 300 | * Other tag renamings:
|
301 | 301 | * `title` -> `titleTag` to avoid conflict with `title` reflected attribute
|
302 | 302 | * `object` -> `objectTag` to avoid Scala reserved word
|
|
0 commit comments