Non breaking spaces everywhere!

[wbear]

Working in live view in the main window (not code), any number of actions cause DW (latest CC version) to insert non-breaking spaces everywhere. If not for the program entering these, I never use them. Literally never.

Example: UL, hit enter to add a new list item...nbsp at the end. Many different things do it. Is there any way to get this to stop? DW still ignores attempts to delete non-breaking spaces in the design window (live view), instead deleting the first character next to it in either direction. This was allegedly fixed, but never released into a mainstream version, AFAIK. 

Need this frustrating and basically pointless practice to stop, as it's doing my head in. 

[wbear]

"Nancy I think did jump the gun a little with her initial post, but you jumped on her imidiatly. "

No, it was her comment about hitting the spacebar that was so ludicrous that started it (prior to that it was very normal; please go look), and telling me to move on as it's not something she sees as a "mission critical" problem. Nothing someone that's upset wants to hear more than someone that's representing the main support (even if volunteer) of a product they use that the thing they consider a bug and is asking for help getting fixed is pointless. It wasn't pointless to me, so dismissing it seemed inappropriate. 

"anyone has not tried them or looked into them deep enough I do not think anyone can comment that they do not do x, y , z when/if they actually do"

Anyone can comment only on what they know, and that's what I did with what I'd tried.
PHPStorm has come the closest, but it's a twitchy setup and not as much in app, as calling external things to work in app that then allows in-app viewing in a separate window/pane. It's hand coded source development, which for me is slower than DW and fix source (slow typist, prone to accidental space bar hits, apparently). At the time of my post, I hadn't looked into it yet. Seems it also has SFTP, but seeing how the setup of just the program itself was pretty complex, it's been slow going. 

Less convenient than DW, but may be a way out. 

[Liam Dilley]

DW for sites outside older style basic ones in my view is a terrible idead in 2021 🙂 but anyway...
- Nancy has given a solution to avoid the issue so can only be a good nice thing there.

- There is an issue and you done a bug report but I think some form of extra entity output has existed in various parts of DW for years just as various WYSIWYG editors are still to this day not perfect in regard to their html output as well.

@Nancy OShea - There are clearly not perfect output for DW and boostrap 3. Great some do not have issues but using all of 4 and now 5 I can see people on the web commenting in regard to a variety of issues in DW so it is definatly not 100% by a fair margin in some cases.

[B i r n o u]

The answer to provide to the OP, it seems to me, was however simple. "Indeed, this is some how a bug!"

Answering, "...if you can't live without it... or... switch to another display mode... or... look at the forum works worse... "

Adding a three points bullet list ... concerning the working environment, the user's forum role... or how to post a vote for improving the queries...

All this remarks related to the barriers due to the various languages we all have... leads for me to a beautiful ...

"...wow... what's going on here ?.... just acknowledge a nice bug... no more... no less...."

But perhaps... I miss understood what was said... or what was going on ?....Or perhaps, that generating a non invoked white space is a normal behavior.. and that it is not a bug in that case... in my lap ... I'm sorry.

[B i r n o u]

but... please beeing quite simple is somehow... easiest...

[Liam Dilley]

Just going through this thread myself.
Ignoring the DW issue.

&nbsp - Non Breaking Space - 100% a html entity, from day one. No one can say it is not.

Nancy at this point in the thread I do not think is being hostile but has jumped the gun a bit in terms of what you feel is an issue with DW in your example.

[wbear]

"&nbsp - Non Breaking Space - 100% a html entity, from day one. No one can say it is not."

Did someone say it isn't? Nancy said "normal" spaces had an HTML entity also: "nbspc". Maybe that's what you're referring to?

[B i r n o u]

&nbsp - Non Breaking Space - 100% a html entity, from day one. No one can say it is not.

By @Liam Dilley

@Liam Dilley  that's not the point, of course   is an HTML entity, nobody said otherwise....

the problem since day one (as you call it) is that this entity is automatically generated by the live editing mode (whether it's a paragraph or the last item of a list) and this, without asking for it, and especially without pressing the space bar...

so the OP ( @wbear ) has always asked the question about how to get rid of this unwanted white character from the live view window.

Then the conversation went into a deaf dialogue... without answering to the original request

[B i r n o u]

You no doubt hit the spacebar which is what produces the html entity for a space. 

By @Nancy OShea

@Nancy OShea , if you give it a try...you'll see that no need to hit the space bar... the entity is created by itself. It's a bug

[Jon Fritz]

Visit the bug report forum here: https://dreamweaver.uservoice.com/forums/382851-adobe-dreamweaver-bugs

Create a new bug report. Be as descriptive as possible about the method you're using to get the nbsp to show up (don't skip any steps, no matter how small they seem) so the devs can replicate it on their end (which they should be able to do without a problem).

Post a link to the bug report here so people can find it and add a vote to it.

With enough people chiming in, Adobe will move it up the list of fixes and hopefully get it taken care of sooner rather than later.

[wbear]

Thank you, Jon. The last one I submitted languished without votes or action for quite a while (since February). The previous one I'd submitted was about the paragraph issue touched on in this thread. To date, no responses. 

OK, just tried. Filled it out, submitted, and it sent me a "magic link" to verify and log in. 

Unfortunately, that link errors out as broken, and I can't. I'd add that to the bug list, but...

Thoughts?

[wbear]

Had to use a different email program to get the link to work. 

Here's the new bug report (which may take time to appear):

https://dreamweaver.uservoice.com/forums/382851-adobe-dreamweaver-bugs/suggestions/43690500-non-brea...

[Jon Fritz]

Voted for both.

Hopefully they'll fix it without introducing a new set of bugs.

[wbear]

lol, too true. 

Thanks Jon.

[B i r n o u]

voted twice too... but I don't belive anything will move on any direction and that vote number will stay the same

[Gail5ECD]

I have noticed this myself when editing in design view so I have to revert to code view in order to take out the NBSs, annoying and shouldn't be there. Thanks for bringing it up and doing something about it.

[B i r n o u]

so much noise for all that... wow... wouldn't it have been simpler to declare, and admit the bug... impressive.

[senzan]

Glad im not the only one experiencing this idiotic problem.

This infuriating bug is still happening over a year since this post. How is it this software has gotten worse rather than better...

[Jon Fritz]

Unfortunately, DW is now in a no-real-development Limbo.

Adobe has no plans for new features or bug fixes. Going forward, they're only concentrating on security patches and OS compatibility updates, if needed.

[wbear]

Adobe has no plans for new features or bug fixes. Going forward, they're only concentrating on security patches and OS compatibility updates, if needed.

By @Jon Fritz

21.3 (which was a really long time coming) fixes some bugs in Mac. Nothing for Windows users.

As for fixes, like the latest "security fix" where they tanked all SFTP connections to even slightly old implementations of OpenSSH? Decided to remove all support for older protocols, without informing users during or prior to the update to 21.3, unless you were following the pre-alpha-release discussion....

Show of hands, how many DW users do that? 😉

The writing is on the wall here. Dreamweaver will eventually be dropped when users get tired of all the issues and lack of attention and stop using it, giving Adobe the excuse to kill it off. Shame. This was the last of the products in the CC collection that was tricky for me to replace with an equivalent. If it goes, so do I. Save a good amount of money per year.

[BenPleysier]

Many `Dreamers` have moved on. The majority of avid developers have gone to Visual Studio and Wappler, while the majority of designers have gone to Wordpress, Webflow and ilk. 

[wbear]

I find it remarkable with the amount of money to be had in leasing this product that they can't do anything with it that would compete with things like Wappler (considerably more expensive at $39/m, slightly cheaper then DW for the watered down version at $19/m). The real plus with DW was always the ability to keep track of all the content as well as keeping in sync with the server. Since they decided to make it harder (if not impossible) to sync now...well...decision becomes easier. 

I'll likely be moving to doing my coding in PHPstorm, which has previewing that actually works. A bit tricky to set a site up, but has SFTP, sync and so on.

[Nayan_Kankariya]

Hi @wbear,

With Dw 21.3 update, we have upgraded OpenSSH to version 8.8, and for the SFTP connections with deprecated OpenSSH procotols, we have provided a workaround for enabling the SFTP connections to remote servers which are still configured with deprecated OpenSSH algorithms. Please refer to the below KB article for details.

SFTP troubleshooting page: https://helpx.adobe.com/dreamweaver/kb/troubleshoot-sftp-server-connection-issues.html

Have a pleasant day!

Regards,

Nayan

Dreamweaver Team

[wbear]

So, the changes that broke SFTP connections gets addressed in a thread/topic about non breaking spaces and all the usability issues they're causing? That one thing is what gets your attention here? Clearly you're reading the complaints about the product, so why is this not addressed in any way?

[J2548728455jw]

I am totally with wbear here and share his frustration. Like him I have used DW since early Macromedia days. I know I could use design view, but I am paying for a premium product and expect live view to work. It doesn't, not properly. I spend large amounts of time switching over to design view because live view has, apparently without logic, added breaking spaces. Live view might be looked down on by the coding purists, but for those of us who have little time it can be a great productivity tool. For example, if I have to add a paragraph into an article, and style some of it with <strong> and <em>, and add a link, I can do all this without writing a word of code in live view, as if I was using a simple word processor. But DW's insistance on adding non-breaking spaces, almost it seems at random, takes the shine off it. I came upon this post because I was looking for a way to turn off this behaviour in Preferences, but presumably there is not one. Moderators on this forum acting in denial that this is any way a problem do rather shake my faith in DW, especially given the recent bug in DW 21.3, which will not allow me (and many others) to upload anything over a few kB (and worse, deletes it off the server when you try!). Like many others I have had to revert to 21.2. But again, DW do not admit this is a bug. I fear a previous comment may be correct - DW is being wound down. In a way it would be a relief, as I can use Affinity Publisher, Photo and Designer instead of Adobe products (I use FCP for my film work any way) and thus no longer need an Adobe sub.