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
Browser/version (+device/version):
Google Chrome Version 108.0.5359.124 (Official Build) (arm64)
Any other tested browsers/devices(OK/FAIL):
Microsoft Edge Version 108.0.1462.54 (Official build) (arm64)
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
Add UploadSet control
Drag file to the Drag-a-Drop area (rectangle with blue borders) and don't drop file to this area and return file back to the folder (see attached video).
What is the expected result?
Drag-a-Drop area should disappear, like in the previous versions (1.98 and older).
What happens instead?
The Drag-a-Drop area stays on the screen (rectangle with blue borders)
Any other information? (attach screenshot if possible)
Screen.Recording.2022-12-21.at.10.39.22.AM.mov
The text was updated successfully, but these errors were encountered:
thank your for submitting this issue. I was able to reproduce it in all versions since OpenUI5 1.100. I forwarded this issue to the corresponding development team and they will contact you in case of further questions.
OpenUI5 version: 1.108.2
Browser/version (+device/version):
Google Chrome Version 108.0.5359.124 (Official Build) (arm64)
Any other tested browsers/devices(OK/FAIL):
Microsoft Edge Version 108.0.1462.54 (Official build) (arm64)
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
What is the expected result?
Drag-a-Drop area should disappear, like in the previous versions (1.98 and older).
What happens instead?
The Drag-a-Drop area stays on the screen (rectangle with blue borders)
Any other information? (attach screenshot if possible)
Screen.Recording.2022-12-21.at.10.39.22.AM.mov
The text was updated successfully, but these errors were encountered: