OLD | NEW |
(Empty) | |
| 1 #### 0.11.4+2 |
| 2 * Don't inline type="css" imports. |
| 3 |
| 4 #### 0.11.4+1 |
| 5 * Fix erroneous messages about invalid package paths in html imports |
| 6 [72](https://github.com/dart-lang/polymer-dart/issues/72). |
| 7 |
| 8 #### 0.11.4 |
| 9 * Update to analyzer `<0.26.0`. |
| 10 |
| 11 #### 0.11.3+1 |
| 12 * Fix bootstrap to return the result of the original main. |
| 13 |
| 14 #### 0.11.3 |
| 15 * Add support for the new `link[rel="x-dart-test"]` tags from the `test` |
| 16 package to the transformer. |
| 17 |
| 18 #### 0.11.2 |
| 19 * Copied `DomProxyMixin` from `custom_element_apigen` to this package and |
| 20 renamed it `CustomElementProxyMixin`. This can be mixed into any class that |
| 21 is using the `@CustomElementProxy` annotation and provides easy access to |
| 22 the underlying javascript element via the `jsElement` getter. For instance |
| 23 the following is a simple example of a dart class that wraps a custom |
| 24 javascript element `foo-element` with a method `doFoo` and a property `foo`. |
| 25 |
| 26 @CustomElementProxy('foo-element') |
| 27 class FooElement extends HtmlElement with CustomElementProxyMixin { |
| 28 FooElement.created() : super.created(); |
| 29 |
| 30 void doFoo(int arg1) => jsElement.callMethod('doFoo', [arg1]); |
| 31 |
| 32 int get foo => jsElement['foo']; |
| 33 void set foo(int newFoo) { |
| 34 jsElement['foo'] = newFoo; |
| 35 } |
| 36 } |
| 37 |
| 38 #### 0.11.1+3 |
| 39 * Switch `html5lib` package dependency to `html`. |
| 40 |
| 41 #### 0.11.1+2 |
| 42 * Added a runtime warning about bad packages paths in html imports to |
| 43 `initWebComponents`. |
| 44 |
| 45 #### 0.11.1+1 |
| 46 * fixes unknown HTML elements if using interop_support.js |
| 47 |
| 48 #### 0.11.1 |
| 49 * Added `initWebComponents` function which performs html import aware |
| 50 initialization of an application. This is done by crawling all imported |
| 51 documents for dart script tags and initializing them. Any applications using |
| 52 this package should switch to this method instead of calling `run` from the |
| 53 `initialize` package directly. |
| 54 * You may also now just export `package:web_components/init.dart` to |
| 55 initialize your app, and then stick your startup code inside a method marked |
| 56 with `@initMethod`, for instance: |
| 57 |
| 58 library my_app; |
| 59 export 'package:web_components/init.dart'; |
| 60 |
| 61 @initMethod |
| 62 void startup() { |
| 63 // custom app code here. |
| 64 } |
| 65 |
| 66 #### 0.11.0 |
| 67 * Add `bindingStartDelimiters` option to the `ImportInlinerTransformer`. Any |
| 68 urls which contain any of the supplied delimiters before the first `/` will |
| 69 be left alone since they can't be reasoned about. If you want these urls to |
| 70 be treated as relative to the current path you should add a `./` in front. |
| 71 * The `ScriptCompactorTransformer` now names its bootstrap file based on the |
| 72 entry point html file, instead of the original dart file. This is ensure it |
| 73 is the original package. |
| 74 |
| 75 #### 0.10.5+3 |
| 76 * Fix normalization of relative paths inside of deep relative imports, |
| 77 https://github.com/dart-lang/polymer-dart/issues/30. |
| 78 * Update analyzer and code_transformers versions and use new mock sdk from |
| 79 code_transformers. |
| 80 |
| 81 #### 0.10.5+2 |
| 82 * Append html imports in front of the dart script tag, if one exists in |
| 83 `document.head`. |
| 84 |
| 85 #### 0.10.5+1 |
| 86 * Fix @HtmlImport with relative paths from within folders in deployment mode. |
| 87 |
| 88 #### 0.10.5 |
| 89 * Update `ImportCrawler` with support for pre-parsed initial documents. This |
| 90 allows it to work better with other transformers in the same step (you can |
| 91 pass in a modified document). |
| 92 |
| 93 #### 0.10.4+2 |
| 94 * Fix `@CustomElement` test in internet explorer. |
| 95 |
| 96 #### 0.10.4+1 |
| 97 * Update `initialize` lower bound to get bug fixes. |
| 98 * Make sure to always use `path.url` in transformers. |
| 99 |
| 100 #### 0.10.4 |
| 101 * Added `CustomElement` annotation. This can be added to any class to register |
| 102 it with a tag in the main document. |
| 103 * Added a `web_components.dart` file which exports all the annotations |
| 104 provided by this package. Note that in later breaking releases |
| 105 `html_import_annotation.dart` and `custom_element_proxy.dart` will likely |
| 106 move into the `src` folder, so switching to the `web_components.dart` import |
| 107 is recommended. |
| 108 |
| 109 #### 0.10.3 |
| 110 * Added `generateWebComponentsBootstrap` method to the main `web_components` |
| 111 transformer file which accepts a `Transform` and a `Resolver`. You can use |
| 112 this function from any transformer and share the resolver you already have. |
| 113 * Fixed up the bootstrap call in `ScriptCompactor` to not use `=>` syntax |
| 114 since it has a declared return type of `void`. This could previously cause |
| 115 a checked mode error if the original program returned something from `main`. |
| 116 |
| 117 #### 0.10.2+1 |
| 118 * Minor cleanup to changelog and tests. |
| 119 * ImportInliner now throws warnings instead of errors. |
| 120 |
| 121 #### 0.10.2 |
| 122 * Added the `HtmlImport` annotation. This can be added to any library |
| 123 declaration and it will inject an html import to the specified path into the |
| 124 head of the current document, which allows dart files to declare their html |
| 125 dependencies. Paths can be relative to the current dart file or they can be |
| 126 in `package:` form. |
| 127 |
| 128 *Note*: Html imports included this way cannot contain dart script tags. The |
| 129 mirror based implementation injects the imports dynamically and dart script |
| 130 tags are not allowed to be injected in that way. |
| 131 |
| 132 *Note*: Relative urls cannot be used in inlined script tags. Either move |
| 133 the script code to a Dart file, use a `package:` url, or use a normal HTML |
| 134 import. See https://github.com/dart-lang/web-components/issues/6. |
| 135 |
| 136 * Added a `web_components` transformer. This should be used in place of the |
| 137 `initialize` transformer if that already exists in your application (it will |
| 138 call that transformer). This will inline html imports (including @HtmlImport |
| 139 annotations) into the head of your document at compile time, it can be used |
| 140 like this: |
| 141 |
| 142 transformers: |
| 143 - web_components: |
| 144 entry_points: |
| 145 - web/index.html |
| 146 |
| 147 If no `entry_points` option is supplied then any html file under `web` or |
| 148 `test` will be treated as an entry point. |
| 149 |
| 150 #### 0.10.1 |
| 151 * Added the `CustomElementProxy` annotation. This can be added to any class |
| 152 which proxies a javascript custom element and is the equivalent of calling |
| 153 `registerDartType`. In order to use this you will need to be using the |
| 154 `initialize` package, and call its `run` method from your main function. It |
| 155 is also recommended that you include the transformer from that package to |
| 156 remove the use of mirrors at runtime, see |
| 157 [initialize](https://github.com/dart-lang/initialize) for more information. |
| 158 |
| 159 #### 0.10.0 |
| 160 * Updated to the `0.5.1` js version. |
| 161 * **Breaking Change** To remain consistent with the js repository all the |
| 162 `platform.js` has been replaced with `webcomponents.js`. Also, the default |
| 163 file is now unminified, and the minified version is called |
| 164 `webcomponents.min.js`. |
| 165 |
| 166 #### 0.9.0+1 |
| 167 * Remove all `.map` and `.concat.js` files during release mode. |
| 168 |
| 169 #### 0.9.0 |
| 170 * Updated to platform version 0.4.2, internally a deprecated API was removed, |
| 171 hence the bump in the version number. |
| 172 |
| 173 * split dart_support.js in two. dart_support.js only contains what is |
| 174 necessary in order to use platform.js, |
| 175 interop_support.js/interop_support.html can be imported separately when |
| 176 providing Dart APIs for js custom elements. |
| 177 |
| 178 #### 0.8.0 |
| 179 * Re-apply changes from 0.7.1+1 and also cherry pick |
| 180 [efdbbc](https://github.com/polymer/CustomElements/commit/efdbbc) to fix |
| 181 the customElementsTakeRecords function. |
| 182 * **Breaking Change** The customElementsTakeRecords function now has an |
| 183 an optional argument `node`. There is no longer a single global observer, |
| 184 but one for each ShadowRoot and one for the main document. The observer that |
| 185 is actually used defaults to the main document, but if `node` is supplied |
| 186 then it will walk up the document tree and use the first observer that it |
| 187 finds. |
| 188 |
| 189 #### 0.7.1+2 |
| 190 * Revert the change from 0.7.1+1 due to redness in FF/Safari/IE. |
| 191 |
| 192 #### 0.7.1+1 |
| 193 * Cherry pick [f280d](https://github.com/Polymer/ShadowDOM/commit/f280d) and |
| 194 [165c3](https://github.com/Polymer/CustomElements/commit/165c3) to fix |
| 195 memory leaks. |
| 196 |
| 197 #### 0.7.1 |
| 198 * Update to platform version 0.4.1-d214582. |
| 199 |
| 200 #### 0.7.0+1 |
| 201 * Cherry pick https://github.com/Polymer/ShadowDOM/pull/506 to fix IOS 8. |
| 202 |
| 203 #### 0.7.0 |
| 204 * Updated to 0.4.0-5a7353d release, with same cherry pick as 0.6.0+1. |
| 205 * Many features were moved into the polymer package, this package is now |
| 206 purely focused on polyfills. |
| 207 * Change Platform.deliverDeclarations to |
| 208 Platform.consumeDeclarations(callback). |
| 209 * Cherry pick https://github.com/Polymer/ShadowDOM/pull/505 to fix mem leak. |
| 210 |
| 211 #### 0.6.0+1 |
| 212 * Cherry pick https://github.com/Polymer/ShadowDOM/pull/500 to fix |
| 213 http://dartbug.com/20141. Fixes getDefaultComputedStyle in firefox. |
| 214 |
| 215 #### 0.6.0 |
| 216 * Upgrades to platform master as of 8/25/2014 (see lib/build.log for details). |
| 217 This is more recent than the 0.3.5 release as there were multiple breakages |
| 218 that required updating past that. |
| 219 * There is a bug in this version where selecting non-rendered elements doesn't |
| 220 work, but it shouldn't affect most people. See |
| 221 https://github.com/Polymer/ShadowDOM/issues/495. |
| 222 |
| 223 #### 0.5.0+1 |
| 224 * Backward compatible change to prepare for upcoming change of the user agent |
| 225 in Dartium. |
| 226 |
| 227 #### 0.5.0 |
| 228 * Upgrades to platform version 0.3.4-02a0f66 (see lib/build.log for details). |
| 229 |
| 230 #### 0.4.0 |
| 231 * Adds `registerDartType` and updates to platform 0.3.3-29065bc |
| 232 (re-applies the changes in 0.3.5). |
| 233 |
| 234 #### 0.3.5+1 |
| 235 * Reverts back to what we had in 0.3.4. (The platform.js updates in 0.3.5 had |
| 236 breaking changes so we are republishing it in 0.4.0) |
| 237 |
| 238 #### 0.3.5 |
| 239 * Added `registerDartType` to register a Dart API for a custom-element written |
| 240 in Javascript. |
| 241 * Updated to platform 0.3.3-29065bc |
| 242 |
| 243 #### 0.3.4 |
| 244 * Updated to platform 0.2.4 (see lib/build.log for details) |
OLD | NEW |