bug for the latest beta, (see my previous post)
bug for the latest beta, (see my previous post)
]]>
© 2024 Lightning Launcher Google+ Archive | DISCUSSION Theme by: 
D5 Creation | Powered by: WordPress
D5 Creation | Powered by: WordPress
< ![CDATA[
It seems to work for me. Does it work on a new desktop with a new dynamic text?
]]>
< ![CDATA[
Works for me too.
]]>
< ![CDATA[
This reminds me…
In color picker, when old color and new color are black, has CANCEL and OK text always been black also?
]]>
< ![CDATA[
Well, as long as edit mode’s active, the app force closes the keyboard (Chris Chastain I’m not entirely sure tho)
]]>
< ![CDATA[
Which keyboard you using?
]]>
< ![CDATA[
I’m using Google Keyboard (and it apparently affects even the stock Samsung keyboard)
]]>
< ![CDATA[
Aha! I’m able to reproduce it.
Guess where? Exactly! On my Samsung tablet.
When I do the steps on the video, on my phone (nexus) the alert is shown and you need to click to open the keyboard.
But when I do it on my Samsung tablet, the keyboard is automatically shown and immediately closed (the keyboard and the alert) as seen in the video.
]]>
< ![CDATA[
TrianguloY o.o So this is another Samsung-specific bug. . . (that’s the second I shot down so far) Could it be another API issue or such?
]]>
< ![CDATA[
In fact Lightning doesn’t request anything regarding the keyboard, maybe if I force the keyboard to appear it would just work. In theory this shouldn’t be needed, but there is something I don’t understand about Android keyboard management. This might be related with focus to, it may not be properly set. I’ll make some experiments on this.
]]>
< ![CDATA[
Doesn’t seem to affect the Note 4 (Android 4.4.4) if that helps anything.
]]>
< ![CDATA[
Pierre Hébert That’s nice to hear. James Coyle Maybe there must be something that somehow renders the Note 4 unaffected by the bug…
]]>
< ![CDATA[
Ah, good news, I can reproduce the issue on a 4.1 emulator.
]]>
< ![CDATA[
Pierre Hébert any word on what’s causing the bug?
]]>
< ![CDATA[
The only word is “Fixed”.
Well, in fact this was a nasty border effect, difficult to explain except if you really wish a technical Android description.
]]>
< ![CDATA[
Well, I think I’d save that explanation for a later date. Thanks tho. 🙂
]]>