Re: Layout not working in Chrome

[John Brownie]

On Friday, 22 June 2012 08:44:46 UTC+10, Kári Emil Helgason wrote:

A few years back I created a keyboard layout I called IcelandicPRO, based on Icelandic but with added keys extensive dacritical support. It was fine until at some point I somehow ruined the Tab button and was never able to fix it. Anyone know anything about that so I can avoid in the future?

Tab is one of the special keys that you normally don't change. It should have the output 	. In the latest version of Ukelele, you can ensure that you have the standard output if you double-click the key and then click the Standard button in the dialog. If you are using the in-place entry rather than the dialog, that option doesn't appear. In the version I'm slowly creating with a Cocoa interface, there's a popover rather than the small entry field, which offers the option to have buttons, so it's there, even though it will take a good while before it gets to actual release.

Recently, I decided to start from scratch, make a more coherent/logical version of my multi-language keyboard and add some basic IPA support to it. It was going fine until my most recent save where I added some combining diacritics and as far as I can tell, that change made the layout not function in Chrome. Is that possible? Did the file somehow get corrupted? What did I do? How do I fix it? My old version works fine in Chrome (save the dead Tab button).

It shouldn't be corrupted, though that is possible. Exactly what doesn't work in Chrome? If you can describe what does and doesn't work, that will help.

Also, what changes have you made between the two versions? Something you did must have made the difference, but it's hard to imagine quite what it would be.

I'm a bit pressed for time at present, as we're getting ready to return to PNG in July, but you can send me both versions and I'll try to have a look and see what is causing the trouble.

John

-- 

John Brownie, john_b...@sil.org or j.br...@sil.org.pg

On furlough in Australia from:

Summer Institute of Linguistics      | Mussau-Emira language, Mussau Is.

Ukarumpa, Eastern Highlands Province | New Ireland Province

Papua New Guinea                     | Papua New Guinea

On Friday, 22 June 2012 08:44:46 UTC+10, Kári Emil Helgason wrote:

Hi guys,

A few years back I created a keyboard layout I called IcelandicPRO, based on Icelandic but with added keys extensive dacritical support. It was fine until at some point I somehow ruined the Tab button and was never able to fix it. Anyone know anything about that so I can avoid in the future?

Recently, I decided to start from scratch, make a more coherent/logical version of my multi-language keyboard and add some basic IPA support to it. It was going fine until my most recent save where I added some combining diacritics and as far as I can tell, that change made the layout not function in Chrome. Is that possible? Did the file somehow get corrupted? What did I do? How do I fix it? My old version works fine in Chrome (save the dead Tab button).

Best,

Kári

[Kári Emil Helgason]

Thank you so much for responding. I was able to fix the tab button in the original version. 

The issue with Chrome was that there was absolutely no input, it was like I wasn't pressing the buttons. I tried a few different apps, Cocoa-based and also others, and it was only happening in Chrome. While I was waiting for you to get back to me, I kept on using the layout without a hitch in WriteRoom. Now, like magic, it's suddenly working in Chrome. I wonder if it the OS wasn't registering/picking it up properly? No clue. Anyway, as of right now, there's no problem. I'll get back to you if it crops up again.

Thanks again for your work on this. Ukelele is extremely helpful!

—Kári

[Geke]

Strange things happening!
The only thing coming to mind is that the combining diacritics
together with the Roman/Unicode type of the layout made things go
awry.
A Chrome update could then have fixed that, who knows.

[Sorin Paliga]

I think this depends on the version of Chrome if only Chrome or only one version of it has this behavior.

> --
> You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
> To post to this group, send email to ukelel...@googlegroups.com.
> To unsubscribe from this group, send email to ukelele-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ukelele-users?hl=en.
>

[new ukelele]

[John Woods]

Now using Chrome 23.0.1271.101, and it seems to work fine in that version. Weird.

On Monday, December 10, 2012 9:59:13 PM UTC-5, John Woods wrote:

I'm getting this same problem. Chrome 23.0.1271.95 for Mac. In my case, it's the standard U.S. keyboard, but modified for Lakota, which has some diacritics. I tried it as both Unicode and Roman, and neither allows me to type in Chrome.

John

[Sorin Paliga]

This is why an eerie behavior should be always cross-checked with various applications, in order to see if the case of an application-specific issue.

--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ukelele-users/-/U918RBVXNg4J.

[politicus]

If anyone is looking for help :
http://productforums.google.com/forum/#!topic/chrome/lkjV1mUV0D4
It worked for me.

HTH.