Confirmed users
1,983
edits
(edits) |
(edits) |
||
| Line 70: | Line 70: | ||
|- | |- | ||
| {{bug|1090454}} Trigger print jobs from the parent instead of the child when printing from a remote browser || Blocks disabling '''write''' access to $HOME and other locations || | | {{bug|1090454}} Trigger print jobs from the parent instead of the child when printing from a remote browser || OSX specific: Blocks disabling '''write''' access to $HOME and other locations || | ||
# For print-to-file (e.g., PDF, postscript). | # For print-to-file (e.g., PDF, postscript). | ||
# Printing to a printer seems to work with write access to $HOME disabled. Without using print_via_parent, using dtrace I saw plugin-container read from ~/.cups/client.conf and write to the content process temp dir ~/Library/Caches/TemporaryItems/Temp-{UUID}. | # Printing to a printer seems to work with write access to $HOME disabled. Without using print_via_parent, using dtrace I saw plugin-container read from ~/.cups/client.conf and write to the content process temp dir ~/Library/Caches/TemporaryItems/Temp-{UUID}. | ||