After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697145 - Crash after pressing 'enter' while editing javascript
Crash after pressing 'enter' while editing javascript
Status: RESOLVED INCOMPLETE
Product: bluefish
Classification: Other
Component: application
2.2.4
Other Windows
: Normal normal
: 2.2.5
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-04-02 20:54 UTC by krizas
Modified: 2014-12-15 18:06 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example file (343 bytes, application/octet-stream)
2013-04-02 20:54 UTC, krizas 		Details

Description krizas 2013-04-02 20:54:43 UTC 
Created attachment 240436 [details]
Example file

Bluefish crashes while trying to edit javascript in a html file. Windows alert 'Bluefish has stopped working' pops-up.

Steps to reproduce:
1)open attached file fragment (happens with full page as well).
2)place cursor after last '}'
3)press 'Enter'
4)bluefish crash on my PC

Bluefish seems to crash every time while trying to start a new line after each "}" in <javascript></javascript> block. This does not seem to happen in other places, for example after '}' in between of the <?php ?> tags.

System:
Windows 7 64-bit
Comment 1 Olivier Sessink 2013-04-03 18:49:10 UTC 
hmm I cannot reproduce this. Can you see if you can reproduce it on different computers?
Comment 2 Christian Tellefsen 2013-04-03 19:30:16 UTC 
Unable to reproduce on Windows 7 64-bit using Bluefish 2.2.4.

Tested:
A) The steps above
B) The steps above, after copying the <script> block into an HTML document (copy, save, restart bluefish, place after '}', press Enter.
Comment 3 André Klapper 2014-12-15 18:06:26 UTC 
(In reply to comment #1)
> Can you see if you can reproduce it on different computers?

Hi krizas, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.