-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom behavior? #374
Comments
Hey there @edsu, sorry I missed this message. This is a very good question, and something we've been wondering about in the past: #109 The key challenge with adding such feature to Scoop is, in my opinion, that it would need to be implemented in a way that is both transparent and easy to interpret. I think modifications made to the live page via the behaviors need, to the extent possible, to be properly logged and clearly explained. Do you have suggestions? Cheers, |
I like how you are thinking about this. Perhaps injecting the behavior itself into the WACZ file, similar to the screenshot, would be a way of self-documenting how the archive was created? |
I'm going to close this since I had missed #109 and it is asking about the same thing! |
I love the usability of scoop. I was wondering if you had considered adding a command line option to inject a custom behavior when archiving a page? For example when archiving this page it would be helpful to be able to click on each image so that the modal displays correctly.
The text was updated successfully, but these errors were encountered: