address feedback

remove containsInlineSidebar prop

fix css name

address feedback

rebase

rebase

used shared logic

address feedback - moved logic into common hook

rebase

address feedback

return null for robotext message

address feedback

address feedback

address feedback

rebase

add afterAll to set default window width and height in tests

add alignment parameter

remove tooltip align styles

rebase

rebase

rebase

rebase

rebase

In D4923#143832, @tomek wrote:

Tested if all the actions work as before.

Have you tested if the set of actions is exactly the same as before?

Used constants from constants file

Used JS constants in styles to support correct measuring size

Change return type to non-optional & add tests

Reabase & address feedback

changed JS styles to CSS classes

removed parameter from onMouseLeaveTooltip

remove redundant check in renderTooltip

Address suggestions after review

For the majority of our contexts we split them into two files: one with context declaration and one with the provider (e.g. keyboard-state or sqlite-context). We don't have a naming convention for these, but probably tooltip-context and tooltip-context-provider would make a lot of sense.

We didn't use this convention for web app. In web app, both menu and modal context were defined together with the provider, so I followed the convention used there. I'm not sure if it's better to keep the context type separated from the provider implementation, but I can separate it if you like.