This is the first report we’ve had of someone using the option you’re using.
I have confirmed it but we’ll have to investigate.
Thanks for your patience and understanding.
I tried a more complicated way and downloaded the webarchive from Safari to local storage and then tried to share the file in the Files App to DTTG - this is possible and DTTG is available as share target.
Very strange
I will try to make some comparisions between the two methods for webarchive creation and I also found the above workaround, but still, I would be happy if you would find the cause and a solution It’s much more conventient to just share from Safari
In case you are interested, I made webarchives from exactly this website on the forum with both methods and the Safari-created webarchive is MUCH larger.
It is possible to first select “webarchive” in Safari and save the result to the Files App. And then, share this webarchive to DTTG.
But why can’t those webarchives not directly be shared from Safari to DTTG?
As soon as I select “webarchive” in Safari, DTTG vanishes from the share sheet.
That’s the questior, problem or bug.
You can see above in the screenshots, that the webarchive that gets generated by DTTG (after sharing the URL to DTTG and selecting “webarchive” within the DTTG share sheet) is simply NOT an archive of the website!
Just have a look at the screenshots.
The DTTG webarchive looks more like a MarkDown version, it is stripped down to text-only.
The webarchive file format is an Apple format, and as such does not have a publicly available specification. DTTG provides a best estimation of this format however it does not support all the features that a Safari generated web archive does such as embedded web archives. As such depending on the web site there may be minor differences in the generated web archives.
But no stress on this, I am perfectly fine with selecting webarchive in Safari… but as as said, it would be great to then directly share to DTTG without the need to save it first and then share again from the Files App.
But of course, if DTTG would have a “Safari webarchive” as option in it’s own share sheet, that would solve the problem too