Yaniv Savir

I've been getting the same or similar issue, but only when using `pry` in RSpec blocks. My input is still being recorded, but none of it is visible. I can...

@MikeBlom Thanks for the suggestion. I inspected our code and I don't see any references to `STDOUT`, `STDERR` or even `STDIN`. I did notice the other day that the visible...

I would greatly appreciate more expansive documentation! The documentation on the [github pages](https://fullscreen.github.io/yt/videos.html) is handy, but it lacks a lot of information. For example, I didn't realize that when using...

Started seeing these more often lately and they are incredibly annoying. They should have a setting similar to the image setting where the content is hidden by default and can...

Has this been implemented? I think I see it in the code, but not it's not in the documentation and the issue is still open. Would be happy to implement/complete...

As a non-coffee script developer, I really appreciated the vanilla JS examples. It would be very helpful to others like me if they were incorporated into the official README.

Getting this error as well. @joshbuddy I re-ran it with `DEBUG=1`. I'm not very familiar with these responses and am not sure which parts are sensitive data. Do you have...

This has been a point of frustration for me as well. I don't like the idea of explicit return values, but what about a config option to run the original...

I don't think you can say "Running the original defeats the point of using a stub in the first place" without acknowledging that that's only one approach. As mentioned earlier...

@JonRowe I would be happy to submit a PR in that style.