Danny Lin 的回应
开发者回应
发布于 6 年前Thank you for the feedback.
The issue on nytimes.com is same as the one with styled components and we are working on it (https://github.com/danny0838/webscrapbook/issues/109). It's a complicated issue as there are many things behind the scene to deal with. We almost have the solution but still need sometime to implement it, maybe next one or two revision.
I can't see an issue for washingtonpost.com, maybe it's really related with the scripts you've mentioned. Could you confirm it (by disabling your scripts and see if the issue's still there) and provide the scripts you are using, for further investigation?
The source page URL is recorded in the source code of the saved page but not shown directly. You'll be able to see it from the metadata if the backend server is used; otherwise you can see it from the source code. We are still investigating an appropriate way to present such metadata without altering the document too explictly.
As this addon site doesn't allow discussion, you can report issues to the source code repo (like the link provided above) so that we can discuss and trace them better:)
The issue on nytimes.com is same as the one with styled components and we are working on it (https://github.com/danny0838/webscrapbook/issues/109). It's a complicated issue as there are many things behind the scene to deal with. We almost have the solution but still need sometime to implement it, maybe next one or two revision.
I can't see an issue for washingtonpost.com, maybe it's really related with the scripts you've mentioned. Could you confirm it (by disabling your scripts and see if the issue's still there) and provide the scripts you are using, for further investigation?
The source page URL is recorded in the source code of the saved page but not shown directly. You'll be able to see it from the metadata if the backend server is used; otherwise you can see it from the source code. We are still investigating an appropriate way to present such metadata without altering the document too explictly.
As this addon site doesn't allow discussion, you can report issues to the source code repo (like the link provided above) so that we can discuss and trace them better:)