[r197] Textbox pin/drag not working

Problem Description

Pinning textboxes while using drag drop behaviour on a sprite or 9-patch will cause the text to "fall" out of the textbox.

Attach a Capx

[attachment=0:2ctq5zbq][/attachment:2ctq5zbq]

Description of Capx

Two textbox pinned to a 9-patch with drag drop

Steps to Reproduce Bug

Drag 9-patch Observed Result Text falls out of textbox.

Expected Result Well.... Affected Browsers
• Chrome: (YES and NW.js)
• FireFox: (Don't know)
• Internet Explorer: (NO) But the textboxes are all over the place, trying to keep up with the 9-patch, but the text stays in place.

Operating System and Service Pack

Windows 7

Construct 2 Version ID

r197

This is a bug in Chrome (and a pretty weird one!), not Construct 2. It works correctly in Firefox and IE11 here, as well as Chrome Canary, so it looks like Google already fixed it and it just needs to make its way down to a stable release.

Ahh ok that cool, ill just keep an eye out for it. thanks

Just letting others know that the problem with textbox text is effected in the Moveto behavior also. When the textbox begins it move across the screen (I only have it moving to a new X with the same Y), it is as if the text itself has gravity pulling it down out of the textbox and it keeps falling until the textbox frame stops moving. The text reaches the X position but now has fallen to a new lower Y height. If I resize the Chrome window even a little, the text refreshes in the center of the textbox again.

Just update Chrome and the problem is gone. Not sure why I did not get an auto update.

This is a bug in Chrome (and a pretty weird one!), not Construct 2. It works correctly in Firefox and IE11 here, as well as Chrome Canary, so it looks like Google already fixed it and it just needs to make its way down to a stable release.

This seems to have been fixed in Chrome now, however my program runs in NWjs v0.12.0 and the problem still exist here is it possible to get it fixed here as well?

nimos100 - no, the bug is in the Chrome browser engine not our code, so the only fix is to update. A new NW.js version should be along soon.

nimos100 - no, the bug is in the Chrome browser engine not our code, so the only fix is to update. A new NW.js version should be along soon.

What do you mean?

The bug is not in Chrome, meaning if I drag it there it works, so Chrome must have been fixed. However if I do the same in NWjs the bug is still there and the text falls out of the textbox or do I misunderstand what you mean or do you mean that you are not developing NWjs so you can't fix it?

The bug was in Chrome. NW.js is based on an older version of Chrome.