Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Camino browser reaches its end

caminobrowser.org

Post reply on HN
Print view View original

101–110 of 127 posts

Re: Camino browser reaches its end

#101

Post by joshmoz »

I worked on Camino quite a bit in the early 2000s, it was a great experience. It's funny to think that we really felt we were contributing greatly to the appeal of Mac OS X by providing the kind of browsing experience Apple should have provided on the OS much earlier, given their focus on it being designed with the Web in mind.

Eventually Mozilla hired me to help re-write the Firefox port to Mac OS X because the product lagged so far behind Camino. Once I got deep enough into that project my Camino contributions dropped off. Dedicated volunteers carried on. I had forgotten that they still hadn't shut it down yet.

Anyway, congrats to Camino on the long run! It was a great option, particularly for earlier Mac OS X users, and a joy to work on.

Re: Camino browser reaches its end

#102

Post by rpgmaker »

as_if wrote: post #97
twic wrote: post #85

Earlier quoted context omitted.

I know! How does he manage to have so few?

he's one of the people who partly (because he's still over 10 tabs) gets the current bookmark-systems in browsers. For most users the bookmarks seem to be broken/too complex. Never had the problem, maybe because I'm going crazy when I got over 10 tabs and want to get rid of them ASAP. :\

Just looking around reddit you easily pass the 50 tabs threshold.

Bookmarks are far from ideal (at least in firefox) and technically you don't need them today since the history works well in case you need to find something (just typing related terms on the address bar) but the history is erased quite often so it's better to have certain urls bookmarked and using the aforementioned address bar to find what you're looking for (or the search on the bookmarks manager). It works for me.

Re: Camino browser reaches its end

#103

Post by progrock »

kmasters wrote: post #69

Give Opera Next a chance. I have been using it since it came out and although it has a couple rough edges it feels more user focused than Chrome.

One rough edge is that it totally ignores my keyboard layout for keyboard shortcuts. It appears to use the Qwerty layout for shortcuts, even under a different layout.

(That's Opera next 12.50 on Linux, with Presto)

Re: Camino browser reaches its end

#105

Post by vvhn »

vvhn wrote: post #94
pilif wrote: post #88

Earlier quoted context omitted.

> You will find this behaviour in all Apple provided applications as well. not on my machine. As I said, I used ~/Library/KeyBindings/DefaultKeyBinding.dict to change it. If the OS provides a way to change defaults, I expect applications to respect that too - no matter the historical reasons. > >in the new Gmail compose window, not even Command-Left/Right works > cntrl-a and cntrl-e work. Yes, but Command-Left/Right…

If the application overrides the defaults (which is fairly common ), your changing the defaults does nothing (for that application and for the keys that might have been overridden). It sounds like Firefox overrides the defaults completely but in it's override "map" keeps some of the functionality the same as the default. I havn't used it but this claims it will change the Firefox behaviour as well (specifically make…

Better link

http://www-archive.mozilla.org/unix/customizing.html#keys

sounds like

cmd_beginLine cmd_endLine

are what you need to modify in the example given

Re: Camino browser reaches its end

#106

Post by jlmendezbonini »

pilif wrote: post #35
eightyone wrote: post #5

Earlier quoted context omitted.

I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…

The one thing that drives me mad about Firefox on the Mac is it's Home/End behavior. Ever since migrating to the Mac, I have remapped the keys to work like on windows and Linux (operating on the current line instead of the current document). You can do that using a custom key binding in ~/Library/KeyBindings. Firefox ignores this and still insists on home/end working on the full document. But even worse: in the new G…

> ...new Gmail compose window, not even Command-Left/Right works (it does in other Textareas - no idea what Google did here)

It drives me crazy too. At one point I used a workaround mentioned in the bug discussion[1], but I have no idea if it still works. I decided to support Mozilla/Firefox and just got used to control+a/e within Gmail.

[1]https://bugzilla.mozilla.org/show_bug.cgi?id=289384#c63

Re: Camino browser reaches its end

#107

Post by brokenparser »

iSnow wrote: post #52
dietrichepp wrote: post #23

Earlier quoted context omitted.

For a surprisingly long window of time, IE Mac was the best browser around. Apparently, it did not share a code base with Windows IE, which explains why IE Mac had all the features people were drooling over in 2001 like full PNG transparency and good CSS support. PNG support even included color correction, and IE Mac did not suffer from the "box model" bug that affected IE on Windows. I think the Mac version of IE ha…

Unfortunately it had the most annoying bug in that it did not reload CSS files. Back in the day, I developed with a text editor on mac PowerBook and after changing one CSS statement, I had to close the browser and restart it.

MacOS had a built-in web server. You could've used that.

Re: Camino browser reaches its end

#108

Post by brokenparser »

duaneb wrote: post #22
theatrus2 wrote: post #20

Earlier quoted context omitted.

It also was the most standards compliant and performant IE of its time, being a totally different code base.

Possibly because they had to please Apple AND Microsoft?

No. It's because MSIE for Windows wouldn't run on MacOS and they couldn't use Wine. (MSFT would never do that.)

Re: Camino browser reaches its end

#109

Post by mortenjorck »

wwweston wrote: post #53
dietrichepp wrote: post #23

Earlier quoted context omitted.

For a surprisingly long window of time, IE Mac was the best browser around. Apparently, it did not share a code base with Windows IE, which explains why IE Mac had all the features people were drooling over in 2001 like full PNG transparency and good CSS support. PNG support even included color correction, and IE Mac did not suffer from the "box model" bug that affected IE on Windows. I think the Mac version of IE ha…

> and IE Mac did not suffer from the "box model" bug that affected IE on Windows. Nope. Just the box model bug that affected all the CSS 2 compliant browsers. ;) It was indeed a pretty good browser for its time, though.

For all the woe brought upon the web by Internet Explorer 6, the "box model bug" is indeed the one thing it did right. It took far too long for everyone else to admit the error and move ahead with the box-sizing CSS spec.

Re: Camino browser reaches its end

#110

Post by Zarel »

dietrichepp wrote: post #23
GigabyteCoin wrote: post #18

Earlier quoted context omitted.

IE for Mac? That has to be an oxy moron of some sort.

For a surprisingly long window of time, IE Mac was the best browser around. Apparently, it did not share a code base with Windows IE, which explains why IE Mac had all the features people were drooling over in 2001 like full PNG transparency and good CSS support. PNG support even included color correction, and IE Mac did not suffer from the "box model" bug that affected IE on Windows. I think the Mac version of IE ha…

Ehh, IE5:Mac may have been better than IE5:Win, and yes, its CSS and PNG support were ahead of its time, but it was still IE5.

IE5:Mac didn't have support for a lot of things IE6 had that we now consider standard, like :hover for links, for..in, Array.prototype.splice, XmlHttpRequest, contentEditable...

Post reply on HN