Cut redstone doesn't de-power for one tick

Just to be super explicit about it, The cut wire DOES eventually de power, but shouldn't it de-power immediately, not wait a tick or two?

Its actually not the redstone not getting de-powered for 1 tick.
Its just the repeater taking a signal from it.
If you set this up with 2 repeaters coming from the block
in each orientation, you will see that some do take a signal and some dont.
So its not the dust's fault, its the repeater's fault.

Dear Dico Karssiens, This is NOT a pre-existing bug and I can prove it.

http://www.youtube.com/watch?v=Jk1rp8FmJN8

This video illustrates the difference between the redstone getting cut in 1.4.7 and the pre-releases of 13w0x. Something has indeed changed and it has to be looked at. I'm sure that this is not the only use case where powered redstone getting cut needs to be consistent.

Also, if you watch the video, there is NO repeater in this setup. it's very simple.

Yes, the error is still present in 1.5

Confirmed with the setup and orientation seen in the screenshot.

Sorry, For some reason, I didn't see the updates in my email. I just tested it and it is still present in 1.8.1-pre3, but since the rest of the redstone community isn't complaining about it, perhaps it just isn't something that's supposed to be fixed.

Reopened, thanks. It's still an issue nontheless.

Still an issue. It last worked in release 1.4.7, Has been broken since 1.5.0.

But it's nearly been three years, so what's the point of fixing it? Everyone's already gotten used to this particular redstone mechanic, so fixing it would probably create even more tickets

This is a bit like quasi connectivity IMO as it is useful for pulse limiters.

Still in 1.9.4 ("on" and "off" screenshots, same contraption but in different directions/mirrored, diamond blocks moved, gold blocks didn't)

disregarding my comments from before, I wonder how fixing this bug would speed up some redstone contraptions?? hmmm....

I just tested the bug with the simple design of the two high smart piston from the video. In the current version, 1.12, it is not the case anymore, that the redstone dust doesn't get unpowered.
It is true, that the two high smart piston does not work in that way anymore, but that is not because the redstone dust doesn't get unpowered, it's because the off pulse is too short for the torch to react. If you attach a dropper directly to the output, it will fire.
So while the behavior compared to 1.4 obviously changed I do not think, this should be considered a bug. The redstone wire changes state as expected and I assume that the created pulse is actually a 0 tick pulse which means, it is too short for even a 1 tick repeater to react.

An alternative design that works similar can be seen here:

Okay reviewing the ticket, from the screenshots:

It is not true that the redstone dust stays on for one game tick. The repeater will update, but it is actually a 0 tick. So this issue should be marked as Dupe of MC-8328.

It is correct in the sense of game ticks.

Marking as related instead.