News for hackers. Stuff that matters.
Re:Does Not Work by Tade0 on Saturday January 28, 2017 @07:38PM (#13510784)
> If you are experiencing a problem of the nature of one of the first two in that list (does not compile or has a run-time exception), then somewhere, you’ve got an error message or an exception, and probably even a line number.

Thing is, in this particular project I'm in - most of the time - you don't.

Since our project is an in-browser text editor most of our bugs occur because the browser did something unexpected, like suddenly changed the selection, or inserted an element somewhere. In situations like these you usually don't get an error message or anything - just weird behaviour.

Normally our users report this by writing that pressing a button or using a shortcut "does nothing" - and that's fine.

When you're dealing with leaky abstractions on a day-to-day basis you sort of have to get used to bug descriptions like these.

Re:Does Not Work by notatoad on Saturday January 28, 2017 @08:14PM (#13511008)
reporting that a particular button "does nothing" is a great bug report (from a user. from a colleague it's a little disappointing). It tells you the three important things you need for a bug report : what did you do, what did you expect, and what actually happened?. The problem with "doesn't work" is that it could mean anything, from "does nothing" to, to use the example in the article, "it launches missiles".
Re:Does Not Work by bastawhiz on Saturday January 28, 2017 @08:26PM (#13511077)
Browser WYSIWYG editors are full of dragons. I'd give you that exception.
Re:Does Not Work by ehnto on Sunday January 29, 2017 @01:39AM (#13512642)
Which is amazing since it's a problem we have been trying to solve for more than a decade. I figure we just can't solve it fast enough to keep up with browser features and bitrot.

I once built a wysiwyg editor that utilized drag and drop for dynamic page content. Native browser drag and drop is an utter mess.

Re:Does Not Work by Tade0 on Thursday February 02, 2017 @03:48PM (#13554506)
Native selection, even if you don't support legacy browsers is a bigger one.

The API itself is ok. It's all the tiny differences between browsers that turn it into a dumpster fire.

And don't get me even started on pasting stuff from Word. Customers expect this to work, because yeah, how hard can this be really? Regardless of how many safeguards you put, eventually someone somewhere is going to create a file that will generate a heap of errors.

We have over 150 test cases(600+ unit tests) and still every week something pops up.

Re:Does Not Work by haimez on Sunday January 29, 2017 @12:28AM (#13512351)
Sounds like you need a managed runtime. Wait... You already have one, it's just a bigger problem than solution. Hrm... Have you considered making a real IDE?
Re:Does Not Work by Tade0 on Thursday February 02, 2017 @03:49PM (#13554518)
Funny you mention this. I took three weeks vacation to do just that, but after ten days I realized that there's waaay more work than I have time for.