Render More Attributes (ng-*)
See original GitHub issueCurrent rendering:
div.well.ng-scope > div.ng-scope > div > button.btn.btn-lg.btn-primary
For angular and others it would be nice to include some attributes like ng-click
and friends:
div.well.ng-scope > div.ng-scope > div > button.btn.btn-lg.btn-primary[ng-click="uploadFile()"]
Originally reported here: https://github.com/getsentry/sentry/issues/3220
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Re render html when adding new angular attribute
my problem is basically make the compiler getting a new attribute i've added in a directive. I'm using typescript and i have something...
Read more >Attribute binding - Angular
With attribute binding, you can improve accessibility, style your application dynamically, and manage multiple CSS classes or styles simultaneously.
Read more >Everything you need to know about ng-template, ng-content ...
The select attribute selects the type of content that will be rendered inside a particular <ng-content> . Here we have first select to ......
Read more >Angular Directives - W3Schools
AngularJS directives are extended HTML attributes with the prefix ng- . The ng-app directive ... Read more about the ng-model directive in the...
Read more >ngOptions - AngularJS: API
The ngOptions attribute can be used to dynamically generate a list of <option> elements for the <select> element using the array or object...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi there. For complex UI, the click breadcrumbs don’t have enough detail - can you not include the XPATH of the element that is clicked? Otherwise its sometimes not possible to work out which element was clicked.
I’ll close this one for now, as we’re aware of this missing piece and we’ll be revisiting how this thing is working in the next major version.
Ref: https://github.com/getsentry/raven-js/issues/783 Ref: https://github.com/getsentry/raven-js/issues/577