5 ms·

Sadly, they removed some power user menu options, like "Open Frame in New Tab".

• cdr 16y ago
  I'm guessing not enough people used them to justify the added complexity - I certainly never used "Open Frame in New Tab". If it's something you absolutely have to have, there's always extensions.
  • pygy_ 16y ago
    > I certainly never used "Open Frame in New Tab". I do on a regular basis, in order to get PDFs out of their frame on the Blackboard system of my university.
    • DTrejo 16y ago
      right click > save as :) I have the same problem, so I feel you.
      • pygy_ 16y ago
        I actually like to have several PDFs open in different tabs. Preview.app (OS X) can't do that.
  • beaumartinez 16y ago
    > To justify the added complexity. Have you had a look at Chromium's source tree[1]? It's huge! I don't know how much complexity they'd save themselves removing a small feature like that (although you never know). Have a look at the building instructions[2] as well. "Due mostly to its history and its complexity, Chromium uses a nonstandard set of custom tools to check out and build." It's a good showcase on the complexity of a browser (and Chrome feels so light and speedy as well.) [1] http://src.chromium.org/viewvc/chrome/trunk/src/ http://src.chromium.org/viewvc/chrome/trunk/src/ [2] http://code.google.com/p/chromium/wiki/LinuxBuildInstructions http://code.google.com/p/chromium/wiki/LinuxBuildInstruction...
    • Andys 16y ago
      I think he meant user interface complexity, not code base.
    • heyitsnick 16y ago
      I think parent meant complexity to the user, not of the code.