Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default element style #265

Closed
nevar opened this issue Aug 4, 2014 · 3 comments
Closed

Default element style #265

nevar opened this issue Aug 4, 2014 · 3 comments

Comments

@nevar
Copy link

nevar commented Aug 4, 2014

http://jsfiddle.net/N74eq/2/

If you check/recheck check box <a> will lose it display style from css.

Here element for get default style don't copy class from original element. Also it maybe matter where we insert element for test.

@BorisMoore
Copy link
Owner

Good catch, thanks! I have a fix ready which will be in the next update...

@BorisMoore BorisMoore added the Bug label Aug 5, 2014
BorisMoore added a commit that referenced this issue Aug 11, 2014
IMPORTANT: This commit corrects an important IE8 bug that was
in the previous commit (55)

This commit also includes some significant updates and improvements:

- New API for creating derived tags - simply specify "baseTag" on
  the custom tag declaration:

  $.views.tags({
    range: {
      // Inherit from {{for}} tag
      baseTag: $.views.tags["for"],
      ...

  See samples: http://www.jsviews.com/#samples/jsr/tags/extend-for
  and http://www.jsviews.com/#samples/tag-controls/range

- trigger=true on data-linked inputs, or two-way binding now uses
  keydown - so data entry updates as you enter each key.

  Setting trigger=true on data-linked inputs, textareas, content-editable
  elements, or custom tags such as {{textbox}} (with two-way binding
  through linkedElem) now triggers immediately after keydown, rather
  than on keyup as previously.
  So setting <input data-link="name trigger=true" />. for example,
  means the name property will update as you enter each character.

- Improvements to DataMap feature. Used for {{props}} tag.
  Examples to follow.

- Support for loading JsObservable (jquery.obserable.js) without JsRender
  for observable-data scenarios without JsViews.

- Support for flexible load sequence for JsViews: Can now load
  JsObservable before JsRender and JsViews, as well as the more
  normal sequence of JsRender, JsObservable, JsViews (as used in the
  single file jsviews.js).

- Many new unit tests for JsObservable.

- {on now supports passing parameters directly to the bound method:
  e.g. {on ... method param1 param2}
  Examples to follow.

- Improvements to contentEditable support.
  Examples to follow.

- Use of autoBind property on custom tags no longer necessary.

- Bug fixes:
  #264
  #265
  BorisMoore/jsrender#238
  #267
BorisMoore added a commit to BorisMoore/jsviews.com that referenced this issue Aug 11, 2014
IMPORTANT: This commit corrects an important IE8 bug that was
in the previous commit (55)

This commit also includes some significant updates and improvements:

- New API for creating derived tags - simply specify "baseTag" on
  the custom tag declaration:

  $.views.tags({
    range: {
      // Inherit from {{for}} tag
      baseTag: $.views.tags["for"],
      ...

  See samples: http://www.jsviews.com/#samples/jsr/tags/extend-for
  and http://www.jsviews.com/#samples/tag-controls/range

- trigger=true on data-linked inputs, or two-way binding now uses
  keydown - so data entry updates as you enter each key.

  Setting trigger=true on data-linked inputs, textareas, content-editable
  elements, or custom tags such as {{textbox}} (with two-way binding
  through linkedElem) now triggers immediately after keydown, rather
  than on keyup as previously.
  So setting <input data-link="name trigger=true" />. for example,
  means the name property will update as you enter each character.

- Improvements to DataMap feature. Used for {{props}} tag.
  Examples to follow.

- Support for loading JsObservable (jquery.obserable.js) without JsRender
  for observable-data scenarios without JsViews.

- Support for flexible load sequence for JsViews: Can now load
  JsObservable before JsRender and JsViews, as well as the more
  normal sequence of JsRender, JsObservable, JsViews (as used in the
  single file jsviews.js).

- Many new unit tests for JsObservable.

- {on now supports passing parameters directly to the bound method:
  e.g. {on ... method param1 param2}
  Examples to follow.

- Improvements to contentEditable support.
  Examples to follow.

- Use of autoBind property on custom tags no longer necessary.

- Bug fixes:
  BorisMoore/jsviews#264
  BorisMoore/jsviews#265
  BorisMoore/jsrender#238
  BorisMoore/jsviews#267
@BorisMoore
Copy link
Owner

@nevar: This has been fixed in Commit 56. The jsfiddle above now works, as does this one http://jsfiddle.net/BorisMoore/N74eq/3/

@nevar
Copy link
Author

nevar commented Aug 12, 2014

👍

Paul-Martin pushed a commit to Paul-Martin/jsviews that referenced this issue Nov 2, 2014
IMPORTANT: This commit corrects an important IE8 bug that was
in the previous commit (55)

This commit also includes some significant updates and improvements:

- New API for creating derived tags - simply specify "baseTag" on
  the custom tag declaration:

  $.views.tags({
    range: {
      // Inherit from {{for}} tag
      baseTag: $.views.tags["for"],
      ...

  See samples: http://www.jsviews.com/#samples/jsr/tags/extend-for
  and http://www.jsviews.com/#samples/tag-controls/range

- trigger=true on data-linked inputs, or two-way binding now uses
  keydown - so data entry updates as you enter each key.

  Setting trigger=true on data-linked inputs, textareas, content-editable
  elements, or custom tags such as {{textbox}} (with two-way binding
  through linkedElem) now triggers immediately after keydown, rather
  than on keyup as previously.
  So setting <input data-link="name trigger=true" />. for example,
  means the name property will update as you enter each character.

- Improvements to DataMap feature. Used for {{props}} tag.
  Examples to follow.

- Support for loading JsObservable (jquery.obserable.js) without JsRender
  for observable-data scenarios without JsViews.

- Support for flexible load sequence for JsViews: Can now load
  JsObservable before JsRender and JsViews, as well as the more
  normal sequence of JsRender, JsObservable, JsViews (as used in the
  single file jsviews.js).

- Many new unit tests for JsObservable.

- {on now supports passing parameters directly to the bound method:
  e.g. {on ... method param1 param2}
  Examples to follow.

- Improvements to contentEditable support.
  Examples to follow.

- Use of autoBind property on custom tags no longer necessary.

- Bug fixes:
  BorisMoore#264
  BorisMoore#265
  BorisMoore/jsrender#238
  BorisMoore#267
BorisMoore added a commit to BorisMoore/jsviews.com-staging that referenced this issue Apr 27, 2015
IMPORTANT: This commit corrects an important IE8 bug that was
in the previous commit (55)

This commit also includes some significant updates and improvements:

- New API for creating derived tags - simply specify "baseTag" on
  the custom tag declaration:

  $.views.tags({
    range: {
      // Inherit from {{for}} tag
      baseTag: $.views.tags["for"],
      ...

  See samples: http://www.jsviews.com/#samples/jsr/tags/extend-for
  and http://www.jsviews.com/#samples/tag-controls/range

- trigger=true on data-linked inputs, or two-way binding now uses
  keydown - so data entry updates as you enter each key.

  Setting trigger=true on data-linked inputs, textareas, content-editable
  elements, or custom tags such as {{textbox}} (with two-way binding
  through linkedElem) now triggers immediately after keydown, rather
  than on keyup as previously.
  So setting <input data-link="name trigger=true" />. for example,
  means the name property will update as you enter each character.

- Improvements to DataMap feature. Used for {{props}} tag.
  Examples to follow.

- Support for loading JsObservable (jquery.obserable.js) without JsRender
  for observable-data scenarios without JsViews.

- Support for flexible load sequence for JsViews: Can now load
  JsObservable before JsRender and JsViews, as well as the more
  normal sequence of JsRender, JsObservable, JsViews (as used in the
  single file jsviews.js).

- Many new unit tests for JsObservable.

- {on now supports passing parameters directly to the bound method:
  e.g. {on ... method param1 param2}
  Examples to follow.

- Improvements to contentEditable support.
  Examples to follow.

- Use of autoBind property on custom tags no longer necessary.

- Bug fixes:
  BorisMoore/jsviews#264
  BorisMoore/jsviews#265
  BorisMoore/jsrender#238
  BorisMoore/jsviews#267
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants