Skip to content

Why do you force the output and errors to be visible after you evaluate an expression? #758

@dylanjcastillo

Description

@dylanjcastillo

Checklist

  • I added a descriptive title
  • I searched for other issues and couldn't find a duplication
  • I already searched in Google and didn't find any good information or help

What is the issue/comment/problem?

I noticed that you force the output and errors to be visible once an expression is executed. But there might be times when you don't want this to happen.

For example, I made an app with two outputs shown in different tabs. Depending on where the user is, only one of the outputs should be visible.

I noticed that whenever I ran a python script or the repl, both outputs would show. Hiding them was not possible only with classes given that you force that by setting style="display:block;". After digging a bit into the code, I found that in lines 577, 578, 602, 603, 24033, and 24034 you set the style setting mentioned earlier and remove the hidden attribute from the output and error elements. In my case, the easiest workaround was just to comment out those lines (see image).

But I was wondering if there's any reason why you set style="display: block;? If this behavior isn't intended, it might be better to use the block class of tailwind or nothing at all.

Metadata

Metadata

Assignees

Labels

backlogissue has been triaged but has not been earmarked for any upcoming releasesprintissue has been pulled into current sprint and is actively being worked ontype: featureNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

Status
Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions