Bug #58899 modified SQL script can be closed without saving

Description:
when loading a SQL script into a "scratch" tab, it can be closed without WB asking whether to save, even when it has been modified

How to repeat:
- Open SQL Editor tab (it opens with a "scratch" edit tab)
- load a SQL script (tab-header is changed to reflect filename)
- type a char or delete some (just make some changes -> notice the correct appearance of the asterisk in tab-header)
- close the tab using the [x] in the tab-header 
no save-question

same happens when you manually create a scratch-tab and then load a script file - it works properly when the active tab is a "SQL Script" tab.

Fixed as of 5.2.35:
+        Closing &workbench; would not prompt to save SQL Editor scratch
+        tabs.

This bug has started reoccurring on 6.3.9 on Windows 7. Closing standard editor tabs (created empty) will display the prompt. Closing tabs created by the Navigator do not show the prompt. An example of a tab created by the Navigator would be right clicking a table and clicking "Select Rows - Limit 500". Typing anything into the SQL Editor does not add the asterisk to the tab, and said tab can be closed either by Ctrl+W or clicking the close button and no prompt appears.

This bug needs reopening for the current version of MySQL Workbench.