Unable to expand groups and open emails on inbox.google.com with `f`

[maximbaz]

Suppose I have a group of conversations on Google Inbox:

I want to expand it, so I hit f:

Finally I press K.

Expected: Group is expanded (like on the picture below)
Actual: Group remains collapsed (just like on the first picture)

Same happens not only with groups, but with emails as well:

Nothing happens when I hit E.

---

Kubuntu 14.10, Google Chrome 39.0.2171.71
b6125a2
I have no custom rules defined in vimium options.

[mrmr1993]

This sounds suspiciously like #1091, but I don't have google inbox to test that theory. Can you try merging #1167 and see if that helps?

[smblott-github]

Confirmed. Also, unfortunately #1167 doesn't fix it.

[smblott-github]

I've only gotten so far as to establish that the selected element is not responding to DomUtils.simulateClick().

[smblott-github]

Off topic (and not a solution to this problem)...

inbox.google.com has good keyboard shortcuts of its own for the basic operations. When the new release emerges (shortly), you can mix and match inbox's shortcuts with Vimium's. These are the inbox shortcuts I'm using:

Other keys (like O, B, etc) are handled by Vimium.

[maximbaz]

True, another approach is to switch into insert mode and use native shortcuts, as we discussed in another thread.
I like the fact that we have many options, still agree with you that this particular issue has to be fixed anyway.

[mrmr1993]

I've only gotten so far as to establish that the selected element is not responding to DomUtils.simulateClick().

Does the element with the link hint have an event listener?

[smblott-github]

Does the element with the link hint have an event listener?

Not sure. Unfortunately, I don't really know how to debug this kind of thing. This is your field of expertise, @mrmr1993.

Here's the element:

[mrmr1993]

This is your field of expertise, @mrmr1993.

We show a link hint for it because it has tabIndex="0". You can check event listeners in the developer tools tab, but if I'm to be the one debugging this, I'd better just give you a script to extract the information:

var eventListeners = [], $0Children = [].slice.call($0.getElementsByTagName("*"));
$0Children.push($0);
for (var i=0, l=$0Children.length;i<l;i++) {
  var el = $0Children[i], eventListenersForEl = getEventListeners(el), hasEventListeners = false, eventListenerStrings = {};
  for (var eventType in eventListenersForEl) {
    hasEventListeners = true;
    eventListenerStrings[eventType] = Array.prototype.map.call(eventListenersForEl[eventType], (function(handlerObj){
      return {
        "listener": handlerObj.listener.toString(),
        "type": handlerObj.type,
        "useCapture": handlerObj.useCapture
      };
    }));
  }
  if (hasEventListeners) {
    eventListeners.push({
      "elementTag": el.outerHTML.replace(el.innerHTML, ""),
      "eventListeners": eventListenerStrings
    });
  }
}
copy(eventListeners);

@smblott-github could you select that element again in developer tools and run this in the console? It will copy a JSON object listing all the event listeners of the selected element and its children to the clipboard. Hopefully there shouldn't be anything sensitive included, but obviously redact it if there is :)

[smblott-github]

Thanks, @mrmr1993.

The console:

And the clipboard:

[]

Redacting sensitive information proved unnecessary!

It looks like all of the onclick handlers are on document or body:

(When you open any of these handlers, you again see that these are attached to document or body.)

[mrmr1993]

Ahh, I hate it when they do this. IMDb does the same for certain UI elements.

I'll try some stuff out with IMDb, and if I have any success hopefully it'll transfer easily to Inbox.

[maximbaz]

if I'm to be the one debugging this ...

@mrmr1993, I can give you an Inbox invite if you need one. If you also need a device to activate it, just create a temporary account, that you would use for development, and I will activate it later today (probably in the evening).

[mrmr1993]

I can give you an Inbox invite if you need one. If you also need a device to activate it

@z0rch I don't have a device to activate it on, so that would be amazing! I'll send the account details to the email address on your profile :)

[smblott-github]

I'll send the account details to the email address on your profile

Copy me (smblott@gmail.com). I can try to activate it now.

If you also need a device to activate it...

Great thinking, @z0rch.