Thanks for the feedback. I tracked down the AV1 failure - RDD isn’t disabled even though we have nothing to provide it. Setting media.rdd-process.enabled = false gets AV1 playback working, and I’ll merge that for a later release. I think we didn’t notice as the hardware codec integration handles all the other big formats, and so not much gets that far. I’m not sure what the implications of that MSE failure are as everything else it does seems to work, but I’ll bear it in mind. It looks like a large part of what’s going wrong there might even disappear before ESR140.
More hands on the browser side would be extremely welcome. I was thinking of doing a system Firefox account plugin at some point, syncing the bookmarks, passwords and such, as a companion to the browser without needing to be part of it. Extensions would be cool, though the UI is so different I’m not sure how compatible they’d be. Might have to package forks in the store for the best blocking extensions. I’ve a feeling it needs a bigger architectural change for Electrolysis/Fission, which we’ve avoided so far, and if that Qt toolkit lands then we should aim to drop ours and use that in the long run. Still a long way to go.
Slipery slope guys, we’re getting off topic
Last word on this for me: I really dislike some actors, hence I never (yes, that does exist ) made any WA account.
I am still alive.
I wish that change of layout were reverted back as it was in SF 1 = long press and hold spacebar to change layout.
I personally like to swipe on keyboard to target letter what i had in plan to type but hit accidentally key next to, so i swipe to correct one and then release finger.
Swipe for left-right to change layout is not good for UX
I agree. The gesture also only makes sense if you use two-three keyboards at most, in most cases probably being the user’s mother tongue, some other language and the emoji keyboard. But as soon as you have more keyboards active, swiping one at a time is pointless. Luckily holding the space bar to select the correct keyboard is still possible.
If you create a feature request to remove the gesture or at least make it optional, you have my vote.
From my point of view even for more than two layouts is the swipe not handy function.
And yes - option to enable/disable swipe to change keyboard lyout would be best solution, but i believe once user will find that he can correct actually pushed character to another one and then release finger so he can save using backspace he will never turn this swipe to change layout to On.
Will check if there is not this request already as the Jolla ruined many good features and UX in SF2/3 …. Even i have xperias with actual SF i still daily driving wih JP1 with SF1x and feeling everytime when i touch actual SF that SF1 is still better in one hand and blind/muscle memory driving for many operations/
I am using 4 different layouts and I wouldn’t want to miss the swiping for changing them. I have also tried using a world symbol (Android) and also the long press on the space key, but I still prefer swiping.
yes, the swipe typing on OKBoard is similar to iPhone behavior what i dislike too. i just like to swipe on keyboard only for correcting typed character - so it is not important where i start touch but important is where i release finger to get typed character (exactly like it was on SF 1.x)
Ok, let’s keep clean and continue talking about Whatsepp (or no Whatsapp) here.
Perhaps can @filip.k or another kind moderator move some posts if needed?
Not yet having a JP2, and this being a thread where owners of the new phone share experiences, I didn’t think asking whether a user’s experience of difficulty with a particular app on the JP2 was off-topic. Especially since I didn’t know whether it was a native app or Android—when I receive my JP2 I hope to use a fully-native Sailfish experience.
) made any WA account.
and feeling everytime when i touch actual SF that SF1 is still better in one hand and blind/muscle memory driving for many operations/