emberjs / emberjs/ember-inspector

Object inspector title hides `$E` send-to-console action in narrow panes

Open
#2,737 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
969
Forks
292
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When inspecting a component/object in the right-side object inspector pane, the top-level object title does not expose an easy-to-use `$E` / "Send to Console" affordance when the pane is narrow. In practice, the action is only visible once the pane is resized wide enough to accommodate the full component name.

This makes the top-level object harder to send to the console than individual properties, which already reveal their `$E` action on hover.

**To Reproduce**
1. Open Ember Inspector.
2. Select a component with a long name so the right-side object inspector title is truncated.
3. Look at the title/header area in the right-side pane.
4. Notice that the `$E` / "Send to Console" affordance for the top-level object is not visible unless the pane is widened.
5. Compare that with any property row in the same pane, where hovering reveals the `$E` affordance.

**Expected behavior**
The top-level object title should expose a hover-visible `$E` / "Send to Console" action similar to property rows, so the action remains discoverable and usable even when the pane is narrow and the title is truncated.

**Screenshots**
I have screenshots showing:
- the title/header area where the top-level `$E` affordance is effectively hidden in a narrow pane
- property rows where hovering reveals the `$E` affordance as expected

Image
Image

**Environment**
Observed while using Ember Inspector locally in the component/object inspector UI.

**Additional context**
This looks more like a UI/discoverability issue than a missing capability: the object can already be sent to the console, but the top-level affordance becomes inaccessible or non-obvious when the pane is narrow. A hover-revealed affordance on the title would align the top-level object with the existing property-row interaction pattern.

Im happy to whip up a PR for this. before that, I wanna understand if there is any existing efforts!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.