Replace the automatic error list with notification.

[JuriTuuti]

I suggest the automatically opening error list should be replaced with a less intrusive notification to let users know they should check the error list

The help in the bottom part, pops up uninvited and unneeded, much like MS Clippy.

If I am moving things around, or setting up the structure of CSS, or just simply work with anything, there will be times between cutting and pasting, when the code has an error. I know that, and it is obvious - the worst thing that can happen at that time, is the 'help' popping up, literally on top of the part that I am editing if it is anywhere near the bottom of the screen (like it usually is), preventing me from correcting the code -- Pasting a piece of code just in the right place is delicate work, and having your work are covered while you are doing it may break your focus, and create a situation where you just need to Ctrl-Z your way back to the way it was when you started, and try again.

Another example when it gets on the way, is when I am laying out the structure of a CSS file -- which means writing empty selectors. Every time I close a selector, the damn thing pops up and complains about me writing empty selectors. -- I will get to them, but for now, could I please just keep laying out the empty selectors, before I forget what I was doing.

As a temporary solution, I am putting a dummy "padding:0;" in each selector, just so I will not be bothered.

What really bothers me is that this represents a shift from what I loved about Brackets. I chose it over VS Code specifically because it didn’t distract me with unnecessary information and let me focus on my tasks without constantly having to dismiss pop-ups or moving my mouse to close tooltips that cover my code.

I would prefer a clear icon to suggest that I should open the error list instead of constantly forcing it on me when I don't need it. I wonder if reducing the constant error messages might even help speed up the error checking process. As it stands, when I correct a line, it may take several seconds for the margin icon to disappear, leaving me staring at the line, trying to see why it is still flagged. I’ve now gotten into the habit of pressing Ctrl-S after each edit, just so I can clear the margin icons.

[devvaannsh]

You're right! We definitely need to refine our approach so that error notifications are helpful without being intrusive.

Really appreciate your detailed feedback. We'll look into this and explore a more user-friendly solution. Sorry for the frustration this has caused!

[abose]

Thanks @JuriTuuti for the suggestion. Its a delicate balancing act between providing just the right information and some times, we spill a bit more than needed.

Regarding the CSS linting behavior, the errors come directly from the W3C CSS Linter, which can sometimes be a bit too strict. But empty selectors are how you start writing a style class, and having constant pop-ups interrupting that flow can be frustrating.

One possible improvement could be adding an option to suppress certain types of errors directly from the notification itself. For instance, users could choose to temporarily ignore "empty selector" warnings like these in the notification itself while working on CSS structure. Would that kind of control help reduce unnecessary interruptions?

We make UX design decisions based on brackets UX design philosophies that works for most users, but that may not work well for all. We usually refine UX over time with feedback like these.

BTW, you can close the problems panel when it is open and the error window will never come back unless you click on the ! icon (same as in brackets)

[JuriTuuti]

That [x] permanently closes the panel is a huge help, and really solves 90% of my problem.

that said, the real-time error checking can be a problem, given that there will inevitably be passing errors while the code is being edited. And there is the amount of resources it takes - I tried to look at some machine created html to see how the selectors are named, but the editor completely choked. And -- the error checking is not really real-time, if the error markers linger in the margin long after the error has been corrected. So maybe there is a reason to take a look at it, and see if it is simply trying to do too much.

That said, being how new Phoenix Code is, I am truly impressed how fast it has been getting better. And the best way to get better is to try things out, and see if they work. So I am totally ok with it.