question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hidden statement inputs seem broken

See original GitHub issue

Problem

If I attach a block to a hidden statement input (reasonably expecting that block to be hidden), the block is programmatically attached to the input, but shown free-floating on the workspace.

Expected behavior

The “visible” flag of the input should cascade down to anything attached to it.

Actual Behavior

Actual behavior is basically “Weird”.

I can verify programmatically that the block is attached to the input, but visually it just appears near the block with the input on the work-space and I drag it around free-form.

This makes hiding a statement input somewhat futile.

Steps to reproduce

I have code like this:

        const summaryInput = this.appendStatementInput("summaryCollection");
        summaryInput.setVisible(false);
        summaryInput.connection.connect(blockToAttach.previousConnection);

blockToAttach ends up showing detached on the workspace (even though it is in fact attached in the block model).

Workaround

As I can’t see a way of hiding a block (looking at the Block API), I’m not sure what the workaround is.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
AnmAtAnmcommented, Jul 11, 2018

«Paraphrasing myself from #1968»

I don’t think Input.setVisible(..) should have been public method. That said, I think we can fix the actual issue so it behaves correctly without expecting extra call from the app developer. I expect it is still an issue if a app developer connects/disconnects to a collapsed block (but I haven’t tested this).

Reopening, but marking it low priority since it is not visible in the UI (requires specific API calls to trigger).

0reactions
BeksOmegacommented, Aug 14, 2021

Fixed by #3806

Read more comments on GitHub >

github_iconTop Results From Across the Web

Hide: and show: appear broken in Harlowe 3.0.2 - Twine Q&A
The following solution relies on using a child passage combined with the (replace:)
Read more >
overflow:hidden on body is broken in ios6
To understand why the fix works, we first need to have a look at how the overflow of the viewport is set. The...
Read more >
CWE-20: Improper Input Validation (4.9) - MITRE
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required...
Read more >
Handling common accessibility problems - MDN Web Docs
Let's look at an example, using Wave. Go to the Wave homepage. Enter the URL of our bad-semantics.html example into the text input...
Read more >
More on data validation - Microsoft Support
In this scenario, you can highlight invalid data by instructing Excel to circle it on the worksheet. Once you have identified the invalid...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found