I opened 6.8.0 today and in the structure panel, elements that have no ID set now have a default ID shown? When was this added?
It's not there in 7.0.0 B2? I'm not even sure it's needed. Might interfere with the quick action icons.
If I were to bet, the "inline updates" you did yesterday or today 
Apparently, they can change more than just AppConnect.
Same here!
I presume the code hasn’t changed, just the display of a fake id?
This makes me wonder, who changed my code???
This is what I did:
<button id="btnLogout" class="btn text-warning" dmx-on:click="serverconnectLogOut.load({});browser.goto('/')">Logout</button>
This is what I see now, have never created a flow myself:
<button id="btnLogout" class="btn text-warning" dmx-on:click="run([{run:{outputType:'text',action:`serverconnectLogOut.load({})`}},{wait:{delay:500}},{run:{outputType:'text',action:`browser.goto(\'/\')`}}])">Logout</button>
Oh sorry this was a side effect for the old Wappler 6.8.0 - with the new Bootstrap extension updates. It is pure visual.
We have added an ID placeholder there to always show ID's if available in the new Wappler (solving this bug) . However in the old Wappler there were unfortunately always default id's internal, so those are displayed.
Again it is pure visual only, it doesn't change anything in code.
2 Likes
While you are looking at automatic id values, maybe elements within a repeat can automatically get unique id’s using the index?
It’s an off the cuff response -I haven’t thought it through-but having Wappler maintain unique element id’s would sure be nice.
1 Like
I'm kindly asking to revert "whatever you did" back for Wappler 6.8.0 users!
1 Like
I’m glad they are not in 7.0.0. They are kind of redundant and cluttering.
Fixed in the latest inline extensions updates.