You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JSPM OR Webpack AND Version
It's an Aurelia Plugin created using the CLI. It's using gulp based build with npm
Browser:
all
Language:
TypeScript 3
Current behavior:
I'm not sure whether it's plugin specific or a general issue, I haven't had the time to test it in a normal app.
Create a custom attribute
Register the custom attribute in global resources
Create a custom component / element
create an element (i.e. div) with an if.bind attribute, make the condition initially false
add the custom attribute to the same element or any child element of it.
start the application, the custom attribute won't be evaluated
make the if.bind-condition somehow true using a button or timeout
the element get's shown but the custom attribute is still not being evaluated.
If the attribute is on an element with initally true for if.bind or a generally visible element, it is working fine.
What is the expected behavior?
The custom attribute should be evaluated / applied / bound / executed even on toggled elements using if.bind
What is the motivation / use case for changing the behavior?
We should be able to hide complex element structures from the DOM and still be able to use custom attributes.
The text was updated successfully, but these errors were encountered:
@BlischkeFlorian@DarkLiKally reading the description in this issue, it seems you want the if attribute to behave similarly to show attribute, is that correct? If so, can you described why you cannot use show attribute?
The issue you reported seems like a common usage to me, so it should have been notified by many others. I'm not sure why it doesn't work for you, so probably we will need the exact code that failed in your project.
I'm submitting a bug report
1.10.3
Please tell us about your environment:
Operating System:
Windows 10
Node Version:
10.13.0
NPM Version:
6.12.0
JSPM OR Webpack AND Version
It's an Aurelia Plugin created using the CLI. It's using gulp based build with npm
Browser:
all
Language:
TypeScript 3
Current behavior:
If the attribute is on an element with initally true for if.bind or a generally visible element, it is working fine.
What is the expected behavior?
The custom attribute should be evaluated / applied / bound / executed even on toggled elements using if.bind
What is the motivation / use case for changing the behavior?
We should be able to hide complex element structures from the DOM and still be able to use custom attributes.
The text was updated successfully, but these errors were encountered: