I'm planning to add full support for iOS (Chrome and Safari). Transferring tabs from apple devices should be possible, just like on android, via the Chrome DevTools Protocol. I'll have to so some research prior to implementing it thought. Here are some resources:
The update will affect how the tool's code is currently structured. Furthermore the name of this very repository will be subject to change after this, to reflect the extended support. The new name will be chrome-tab-transfer.
For now, this is only a planned feature, since I'll have to get my hands onto a real-life iPhone first, but the whole thing should still work the same, regarding the basic steps (i.e. check executable, launch adb/iwdp proxy, download the tabs, write output files and finally do some cleanup).
It might make sense to keep some backwards compatibility with the current command, to keep automation scripts working correctly.
Please note: This is a DRAFT.
I'm planning to add full support for iOS (Chrome and Safari). Transferring tabs from apple devices should be possible, just like on android, via the Chrome DevTools Protocol. I'll have to so some research prior to implementing it thought. Here are some resources:
The update will affect how the tool's code is currently structured. Furthermore the name of this very repository will be subject to change after this, to reflect the extended support. The new name will be
chrome-tab-transfer.For now, this is only a planned feature, since I'll have to get my hands onto a real-life iPhone first, but the whole thing should still work the same, regarding the basic steps (i.e. check executable, launch adb/iwdp proxy, download the tabs, write output files and finally do some cleanup).
It might make sense to keep some backwards compatibility with the current command, to keep automation scripts working correctly.