no caret on google search box (intermittent)

[kevin gunn]

Using unity8 on desktop, noticed that sometimes I do not see a caret upon choosing an editable textbox.
I have one on launchpad no problem.
But on the google home page, if i select the search box in the middle of the screen there is no caret. Also in gmail if i select the search box I see no caret.

The url/search bar is fine, i see a caret there.

[kevin gunn (kgunn72)]

i just tried again and no problem, possibly first launch?

[Olivier Tilloy (osomon)]

No carrot in the Unicode symbols and pictographs, but here is an eggplant: 🍆

[Olivier Tilloy (osomon)]

U+1F955 appears to be reserved for this in unicode 9.0 😊

[David Barth (dbarth)]

Was it a caret problem, or the focus which was not set? ie, could you type into the textfield at all?

[kevin gunn (kgunn72)]

changing title...but thanks for the laugh osomon

[kevin gunn (kgunn72)]

yes, i could actually type in the box - so the focus seemed appropriate, just missing caret

[Chris Coulson (chrisccoulson)]

Do you see the coloured focus ring around the text box when this happens?

[kevin gunn (kgunn72)]

sorry, i don't recall the coloured focus ring. now that you mention it, I'm not sure I can tell it has one normally (color wash?) - anyway I'll keep an eye out for it, and see if it happens again.
Is there any log that would be good to grab if this happens?

[Chris Coulson (chrisccoulson)]

There's a couple of screenshots showing what I mean. The caret only disappears if we don't have focus (ie, the webview is not the focused item in the window, or it is but the window isn't focused). http://start.ubuntu.com/ styles the border of the input field blue when it's in focus - if this isn't happening at when you experience the caret not showing then it confirms it's a problem with focus, which appears to be specific to Unity 8

[Santosh (santoshbit2007)]

I can easily see this issue with unity7.4 also and quite frequently.

With intial debugging, I found
Even if browser window is visible, item_->window()->isActive() remain false quite longer period time, means QuickWindow active property was not instantly updated even after browser is launched.

It doesn't happen always, so when window is set active directly everything works fine

I guess some problem with window managers,

[Santosh (santoshbit2007)]

Is this bug still reproducible with latest ???