Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Clicking on any entry in the kebab menu results in TypeError #9744

Closed
evq opened this issue Jun 27, 2017 · 6 comments
Closed

Clicking on any entry in the kebab menu results in TypeError #9744

evq opened this issue Jun 27, 2017 · 6 comments

Comments

@evq
Copy link
Member

evq commented Jun 27, 2017

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    Clicking on any entry in the kebab menu results in a TypeError, and clicks to switch tabs, etc stop working.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Archlinux AppVM on Qubes, i3 WM

  • Brave Version (revision SHA):
    master (4042f5f)

  • Steps to reproduce:

    1. Click on "settings" in the kebab menu
  • Actual result:
    Browser stops responding to most clicks, the following error is seen in the dev console:

Uncaught TypeError: Cannot read property 'filter' of undefined
    at ContextMenuSingle.render (contextMenu.js:236)
    at ReactCompositeComponent.js?d2b3:795
    at measureLifeCyclePerf (ReactCompositeComponent.js?d2b3:75)
    at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (ReactCompositeComponent.js?d2b3:794)
    at ReactCompositeComponentWrapper._renderValidatedComponent (ReactCompositeComponent.js?d2b3:821)
    at ReactCompositeComponentWrapper._updateRenderedComponent (ReactCompositeComponent.js?d2b3:745)
    at ReactCompositeComponentWrapper._performComponentUpdate (ReactCompositeComponent.js?d2b3:723)
    at ReactCompositeComponentWrapper.updateComponent (ReactCompositeComponent.js?d2b3:644)
    at ReactCompositeComponentWrapper.receiveComponent (ReactCompositeComponent.js?d2b3:546)
    at Object.receiveComponent (ReactReconciler.js?399b:124)
  • Expected result:
    Browser should navigate to the preferences page
  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes
  • Is this an issue in the currently released version?
    Unk
  • Can this issue be consistently reproduced?
    Yes
@luixxiul luixxiul added this to the 0.19.x (Nightly Channel) milestone Jun 28, 2017
@dorin131
Copy link

I am experiencing the same issue and have a fix. Can I make a pull request?

@evq
Copy link
Member Author

evq commented Jun 28, 2017

@dorin131 Please do. I have a work-around (just adding a check / returning null) however a root cause fix would be great.

@dorin131
Copy link

@evq That was going to be my fix :D
But let me try to figure out the root cause and do it properly.

Also, several tests are failing. Is it OK to skip them when pushing this fix and deal with them as a separate issue?

@bsclifton
Copy link
Member

@dorin131 if unit tests are failing, I can help you look at it (as part of the pull request) 😄

@dorin131
Copy link

@bsclifton this doesn't seem to be an issue anymore

@evq
Copy link
Member Author

evq commented Jul 5, 2017

Can confirm that this appears to have been fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.