4 ms·

Please put [PDF] in the title.

• savoytruffle 9y ago
  Out of curiosity, why is this still something people desire in a link? Can't any modern browser pretty much open a PDF as quickly easily as a web page?
  • Crontab 9y ago
    Personally, I feel it is simply good courtesy.
  • jimktrains2 9y ago
    Mobile will download and store on the device. Web pages are quite large anymore and most can be larger than a PDF when delivering less content, so I don't know if there is a size issue anymore.
    • pinum 9y ago
      iOS shows it inline. Android can do too; it usually starts a download instead but IMO that's the browser's fault (should default to embedded).
      • jimktrains2 9y ago
        Is it really a matter of fault when the original question was 'who doesn't not 'why don't they'?
  • zootboy 9y ago
    I personally have PDF rendering disabled in browser for security, just as I have JS disabled by default. So no, my browser cannot display a PDF at all.
    • pinum 9y ago
      To be fair- if you turn off standard features, you can't complain when you get a sub-optimal experience.
      • mulmen 9y ago
        PDFs are a sub-optimal experience. Putting [PDF] in the link just saves me from wasting the time of clicking.
  • exikyut 9y ago
    Principle of least surprise. Web browsers primarily display web pages.
• beefhash 9y ago
  Normally HN does that automatically if a link ends in .pdf, but there's a GET parameter here (m=1) that prevented it from working.
  • deathanatos 9y ago
    That HN doesn't parse out the path prior to checking if it ends in .pdf fills me with warm and fuzzies.