Update to 0.8.0
-
@scottalanmiller said:
@nadnerB said:
Super frustrating on a Mobile screen as it takes up twice as much real estate
I don't know that they have said that they will remove it. Have you posted on the NodeBB forum about it? That would be the way to get some attention.
Haven't yet. Only been a real issue this week as it's a bit different to normal access wise
-
Image uploads are working again.
-
Finally no one ever taught me how to do it so I have so many SW pics to upload!
-
@Minion-Queen said:
Finally no one ever taught me how to do it so I have so many SW pics to upload!
Sweet - Looking forward to seeing them!
-
@Minion-Queen said:
Finally no one ever taught me how to do it so I have so many SW pics to upload!
lol Jaredbusch showed me how at SWorld.
-
Just discovered an composing issue on Window 10 and Chrome.
New text is below the edge of the screen and not visible...
-
@gjacobse said:
Just discovered an composing issue on Window 10 and Chrome.
New text is below the edge of the screen and not visible...
I wouldn't call that new, I've had that issue before with FireFox. I solved it by changing the zoom level of FireFox.
-
@Dashrender said:
@gjacobse said:
Just discovered an composing issue on Window 10 and Chrome.
New text is below the edge of the screen and not visible...
I wouldn't call that new, I've had that issue before with FireFox. I solved it by changing the zoom level of FireFox.
I have had that on Chrome a few times, but on iOS a lot over the last year.
-
right clicking in chrome on windows 10 seems to now have issues when you try to fix spelling issues in the reply box. It seems like it looses focus on that frame and goes back to the main frame so you don't get the spelling options, and you loose your cursor for typing. The only way I've been able get my cursor back to type again after doing this is click and drag a few times til it will highlight text in the box and then use the arrow key. Still can't use the right click on words options though.
-
I see a lot of blame here on Windows 10 - are you sure it's not a Chrome update that caused the issue? Just asking to be fair.
-
@Dashrender said:
I see a lot of blame here on Windows 10 - are you sure it's not a Chrome update that caused the issue? Just asking to be fair.
Yes,. to be fair.
I use Chrome on the NTG PC, and have no issues,..
I just did a good bit of work on my laptop, so it is possible that it is still - even with 'fresh new' installs, that there is a minor difference.
-
The NTG laptop isn't windows 10?
-
-
@scottalanmiller said:
@Dashrender said:
The NTG laptop isn't windows 10?
I think he has a pre-10 laptop.
Aww - I recall you saying that places like NTG need to stay using the current OSes for experience, etc - so I thought it was odd that it didn't have Win 10
-
I know most of us are on Windows 10.
-
The laptop he is speaking of is his personal one.
-
@Dashrender said:
The NTG laptop isn't windows 10?
The laptop is my personal system. the NTG system has been running 10 since April when I received it.
-
@gjacobse said:
I just did a good bit of work on my laptop, so it is possible that it is still - even with 'fresh new' installs, that there is a minor difference.
OK so you have two Win 10 systems, I can't tell from the above statement if it's working on the NTG system or not?
-
@Dashrender said:
@gjacobse said:
I just did a good bit of work on my laptop, so it is possible that it is still - even with 'fresh new' installs, that there is a minor difference.
OK so you have two Win 10 systems, I can't tell from the above statement if it's working on the NTG system or not?
Apologies ... It's still Monday and I haven't had any Mountain Dew yet... Check back with me on Thursday and I might be a tad more coherent..
-
New syntax parsing is stupid..
