It is not possible to print an article directly from NYTimes.com in Safari 12.1. If I turn off Content Blocking for that site, I can print.

Reader will print normally. A bug report has been submitted to Apple.

What, exactly are you trying to do?

I just opened a NYT article and hit command-P, and although I didn't go all the way to paper, nothing unexpected happened, and I successfully saved the article as a PDF.

Same here....and I did it two ways - once just going to the site and once after logging into my account.

I wonder if your problem is caused by a particular ad blocker?

I'm running the AdBlock extension (NOT the app), and it didn't prevent printing, but I remember that Ghostery blocked content that AdBlock didn't, so maybe something like that's your real problem, not Safari.

I'll have to play with the settings for awhile. I just enabled Content Blocker and, with all extensions working, everything seemed to be normal. I'll post back after trying this for awhile.

ADDENDUM: The problem reappeared after enabling Content Blocker. I disabled all extensions and it stays the same. I even tried disabling extensions one at a time (including Adblock and Ghostery) and had no luck. I also, on a whim, repaired user permissions with TechTool Pro. I have no idea about what's going on.

I may have solved this, although time will tell. I deleted the NYTimes cookie and caches, restarted Safari, and logged in. So far, things seem to be OK with Content Blocking enabled and all my extensions active.

I spoke too soon; the problem is back. It returned after I went to another site in the original tab and then returned to NYTimes.

And now, after going back to NYTimes after being at another site (same tab), it's working again.

My fault, but I should have been clearer when I said that I can't print from the NYTimes website. When I either click the Print icon, press Command-P, or go to File > Print, I get the error beep and the print dialog box does not appear.

I don't know if this helps, but there it is.

Here's another wrinkle: Printing articles from NYTimes works if I open the website in a new tab. As soon as I go to another site and return to NYTimes within that tab, printing does not work.

I don't get the "error beep" thing; doesn't that happen ONLY when you're trying to do something that you inherently CAN'T do?

It seems, but obviously isn't, inapplicable in your circumstances.

The beep is the Funk sound. You can sample it in System Preferences > Sound > Sound Effects by double-clicking it. When I click the Print icon in safari, the icon blinks and Funk sounds. And yes, it should only happen when trying to do something that I inherently can't do. Printing should not be in that category!

Which particular sound you use is inconsequential, but your mentioning Funk reminded me that one of my custom sounds is a 2 second clip of someone whistling Dixie. (It took a mess of searching to find it!)

I love knowing that my MBP can do everything including whistle Dixie.

apple's Print in safari is getting dodgy.

and on a growing number of pages, Print -> Save as PDF is becoming downright useless. I've had a few rather frustrating conversations with Apple over this feature churning out a garbled mess on some pages, only to be given suggestions to use other web browsers like Firefox. Apple apparently has NO intentions of fixing the issue, they're content with blaming it all on some insurmountable limitation of web page designs. All I can think of is "if you can manage to print it on the screen, how can it be impossible to print it on the printer?"

You confirmed what my wife has said about Apple. She opined that Steve Jobs would not have let this bug go unfixed. BTW, File > Export as PDF usually works better than Print > Save as PDF. While using Services can be less than satisfactory, it also works, as does printing a screenshot.

Apple asked me for an update on my bug report, which I happily supplied. We'll see if they actually fix anything. On a whim, I emptied the Safari cache (no effect on the issue) and reapplied the Combo 10.14.4 update, also to no effect.

I wonder if it’s not so much an issue with Safari 12.1, but instead the combination of Safari 12.1 with OS 14. Since the start of this thread I’ve done a few prints from Safari, including regular printing and PDF prints, without issue. However, while I’m using the same Safari, I am OS 13.6.

Maybe Apple needs to fix the OS, not the browser.

It seems to be Safari, specifically. I did not have the issue in 10.14.3 and the previous version of Safari (although your point is well taken). The problem does not occur in Firefox, which leads me to believe that it's Safari. By coincidence, I just updated this info (at the behest of Apple) in a bug report. My update is below:

Apple Developer Relations
Apr 3
Engineering has provided the following feedback regarding this issue: Please update this report with new information. There’s no need to create a new one to update it as you did with bug #: 49421896.
Jonathan M. Chuzi
7m
Content blockers appear not to be the issue. I mention NYTimes because that is the first site that I saw the problem with, but it occurs with other sites. Basically, if I open a site for the first time, printing occurs normally. If I navigate to another site and then go back to the first one (using either History or the Back button), I get the Funk sound (impermissible action) whether I click the Print icon, do File > Print, or use Command-P, and the Print dialog box does not appear. However, if I open that site in a new tab, I can print normally. Extensions have nothing to do with this (I tried disabling them and the problem still occurred). This started with Safari 12.1 and does not occur in Firefox.

The bug also exists in Safari Technology Preview 12.2. I have reported it through the beta tester network. (Bug number 49793437)

Apple has responded to my bug report with a request for a sysdiagnoses so they are taking it seriously and working on it.

Excellent! Hopefully, V1 is wrong about Apple apathy with this issue.

Reporting an error using the STP method is a good example of what should go into a problem report the requested data is:

• Product:
• Title:
• Classification:
  • Bug
  • Suggestion
• Bug Type:
  • Security
  • Crash/Hang/Lost Data
  • Power
  • Performance
  • UI/Useabillity
  • Serious Bug
  • Other
• Reproduceability
  • Always
  • Sometimes
  • Rarely
  • Unable
  • Didn't try
• Summary:
• Steps to reproduce:
• Expected Results:
• Actual Results:
• Version/Build
• Configuration:

Some of the items seem repetitive, but as you fill it out this gives a full and complete picture of what is going on. This could help with a lot of the posts on FineTunedMac!

Perhaps this post or a variation of it should be locked and at the top of every forum's index?

Something like this?

Do you think posters would pay any attention to it?

Aaaah, maaaybe, but even a small success rate would be helpful.

I can think of only one change I'd make: At the very top, I'd insert "Before you begin, please shut down and restart your Mac, and see if your problem persists."

Accompanied by the link to the bug reporting page. I, for one (and am probably not alone), have no idea where that is.

You've misunderstood this, ryck; we're discussing a template for posting at FTM.

Apple's bug report page is here.

The macOS feedback page is here.

...and the Apple example I worked from was found in Safari Technology Preview > Help > Report an Issue

Aaaah, now I get it. Thanks for the clarification....and the Apple link. I've just made a mental note: "Try to stay awake when visiting FTM."

Providing the link to bug reporting is going to be very helpful in addition to the template you've pulled from the Technology Preview (that Help > Report an Issue menu choice is not included with normal Safari).

FWIW, I just invested nearly 10 minutes of semi-aimless wandering through the Apple Support site trying to find the Bug Report link without cheating and clicking on the link that artie provided.....I gave up and cheated.

Instead of cheating, try a search engine. I have learned that it is faster to search DuckDuckGo (or Google) than to search Apple's website (and this applies to many sites, especially Adobe and Microsoft).

Yep, I can see that this is going to be an interesting topic....

Doing a Duck Duck Go search reveals that Apple does not provide a simple path for bug reporting to the general public....there were several third party sites that did a deeper dive into what paths were available.

In essence, if you are a registered Apple Developer, there is a direct path that you can use....but if you are not a registered Apple Developer, you are presented multiple directions that are not clearly a means for bug reporting. THIS 2 year old Apple Discussions thread gives links to the Product Feedback path - and THIS Apple Developer link guides bug reporting for that community.

THIS LifeHacker article provides another path to Apple links as well as paths to follow for other software and hardware makers.

I think we need a sticky within FTM to help clarify the process.

Just a note: I think this page is primarily for developers, but I KNOW that it's not to be used lightly.

I was once chastised (Actually, the email I received bordered on nasty!) for reporting an issue that could have been reported at Feedback - macOS - Apple.

A good rule of thumb is that if reporting the isue doesn't require submitting either a screenshot or log, it can probably be directed to the feedback page.

Agreed! This is worthy of some discussion of what should be included. You might want to split this off into its own topic — perhaps in FineTunedMac Feedback?

Found what several others said - first time you open a page you can print, but not the second time unless in a new tab, works in firefox, etc..

Also this time (today) talking to apple got someone competent (4th person I talked to). Person one had me reset printers wanted to wipe computer as try two. Nope not doing that. Person 2 no idea what to try and sent to supervisor who saw no solution in their system. Called back later, guy is some senior something or other who had me try some more stuff including having safari pretend to be another browser - had same problem. So he is sending this on and then plans to check on this in a couple of days to see what they plan to do about it; if they have even been able to figure out how to fix it...

I went through this thread and gave them the various bug reports people had already filed so that this info is consolidated together.