Posts made by drewfx

I'm not having any problems here with wikipedia on 12.18 with javascript enabled.

I haven't come up with a solution, but looking at the network info in Dragonfly, the page request is repeatedly returning:

HTTP/1.1 301 Moved Permanently
.
.
.
Location: Stupid_forum_editor_won't_let_me_type_h_t_t_p_s_without_turning_it_into_a_link://en.wikipedia.org/wiki/Can%27t_Stop_(Red_Hot_Chili_Peppers_song)

In my 12.18, instead of following the redirect it just repeatedly retries the original request (with the ' instead of the %27).

If I enter Stupid_forum_editor_won't_let_me_type_h_t_t_p_s_without_turning_it_into_a_link://en.wikipedia.org/wiki/Can%27t_Stop_(Red_Hot_Chili_Peppers_song) I get the same results.

Based on this maybe someone else here knows of a solution or workaround?

Check that specific font in another program. Twice I've had (I believe) a Windows update lose the default font and had the same result.

OK, I'm glad it seems to be working for everyone (knock on wood)! Please post if this is still causing problems.

I'm going to rewrite the instructions here, with hopefully the correction showing properly by delimiting the asterisks, to make it easier if we want to refer to it in the future.

Workaround fix for Photobucket embedded images not displaying in 12.17

I'm not sure if this will cause any problems for other sites, but try this in 12.17:

• Open the opera:config advanced configuration page.

• Go to the "Network" section.

• Under "HTTP Accept" enter the following string:

image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash, */*

• Hit the save button at the bottom of the Network section.

• See if Photobucket images are working.

Apparently this forum autoformatted and I didn't notice last night, but it shouldn't be "/" at the end but rather asterisk slash asterisk.

See if that helps with any broken sites. Otherwise adding appropriate tags might work, but web development is not my bread and butter.

You can change them by editing the preferences file, but (though harmless) it's not for beginners.

OK - I'm not sure if this will cause any problems for other sites, but try this in 12.17:

• Open the opera:config advanced configuration page.
• Go to the "Network" section.
• Under "HTTP Accept" enter the following string:

image/gif, image/jpeg, image/pjpeg, application/x-ms-application, application/vnd.ms-xpsdocument, application/xaml+xml, application/x-ms-xbap, application/x-shockwave-flash, /

• Hit the save button at the bottom of the Network section.
• See if Photobucket images are working.

I think PB is a little different from most "we don't support your browser" sites because we are talking about embedded pictures that can affect any site on the web. If I post a picture and the "geniuses" at PB can break it for some browsers used by other people that I want to see my picture, both now or at any point in the future (!), why in the world should I use PB?

One of these days I'm going to look back into fixing this, but if I contacted PB I would let them know that if their site is not universally compatible for embedded pics, I will not only not use it myself but recommend that no one else use it either every chance I get.

Technically all they need to do is serve the picture directly for certain browsers. I found that the changing the "accept" tag in the request header can cause them to serve up the picture directly rather than redirect, but then I (temporarily) lost interest in pursuing it.

Upon further review, it's not consistently working

Looking like it may require some userscript...

I don't understand web developers always making things needlessly complicated. You don't need pages of scripting to load a stupid image.

You need to add the site specific preferences for a few of those Photobucket sites I listed because even though you can't always access them directly, the code PB uses to display images runs indirectly off of some of those sites.

If you go to Tools>Preferences>Advanced>Content>Manage Site Preferences and then add those sites listed above and set "Mask as Internet Explorer" for each one (and make sure Javascript is enabled if you don't enable it globally), I think it should work. I got most everything working here the other day by doing so, though I lost interest before I got image editing and the previous/current/next image thumbnails working.

Unfortunately there's a lot of PB sites, and I can't remember exactly which ones fixed this particular problem. I thought it was the one's starting with "i" but it might have been the pbsrc.com ones. It took me awhile so I finally ended up just changing every PB-related site I could find, but embedded images definitely went from not working to working here by changing that setting.

Regarding 12.17, if you set site specific preferences to "Mask as Internet Explorer", the images will display and Photobucket will mostly work.

Unfortunately, there are a large number of Photobucket sites, including the following:

s969.photobucket.com
i969.photobucket.com
s68.photobucket.com
i68.photobucket.com
rs969.pbsrc.com
oi969.photobucket.com
pic2.pbsrc.com
static2.pbsrc.com

I can't remember, but I think the one's starting with "i" fixed the embedded images not displaying issue.

Personally I'm not going to waste time worrying about hackers developing any new Presto specific hacks given its slight market share in most parts of the world and lack of a future.

From the menu:

1. More Tools - Enable Developer Tools
2. Developer Tools - Web Inspector

@drewfx
Which extensions are you trying to create?

Nothing currently, as I don't have enough to desire for it.

The point is just that they are not difficult to create for anyone who can do basic web coding, but the API limits what you can do.

http://dev.opera.com/extensions/tut_getting_started.html

The API info is basically the same as on the Chrome dev site, but Chrome have some sample code too:

https://developer.chrome.com/extensions/samples

I believe it's easier to spend my time just creating one that both works and works the way I want rather than wasting time searching for something and being dissatisfied with it.

I found that though there are some good extensions, in general they are a waste of my time.

There are a few that I use, but after spending much time searching for extensions and reading reviews and installing them only to find out they only worked badly, inconsistently or were tedious compared to 12.17, I decided I'd be better off creating my own extensions (assuming the extension API even supports what I want to do).

I look at Chrome-based Opera as a different browser entirely. It has some advantages, but it's a terrible substitute for Presto-Opera for those of us who actually used and/or depended on some of Presto's unique features.

I use it as my second "compatibility" browser alongside 12.17.

It does seem to be both fast and compatible, and if they restore some more of the old features over time I expect I will use it more and more.

Most of the complaints I have is that it's missing stuff from 12.17 that I loved, but I think that's true of all the other browsers too.

And drewfx, maybe Opera isn't thinking of creating, "the greatest browser ever known to man," but they are a company that wants to make money, and also, I believe they have pride in their achievements -- which have continued with the innovative Coast for Ipad. No reason to think they want to stop their work on desktop Opera. Maybe they do want to save bucks not having to develop the browser engine, but that gives them more flexibility to be creative elsewhere.

Then we agree on something.

wake up to reality. Thankfully Opera has done just that and it will be much better off for it in the long run ... yes, minus a few thousand whining geeks but with tens of thousands of new "average" users who couldn't care less about all the ultra configurable nature of Presto.

If we're going to talk about "reality", personally I think the reality is it was a business decision.

Presto required too big of an ongoing commitment for both maintenance, compatibility and upgrades with declining market share in a desktop market that wasn't expanding. So they decided to cut their losses and build on top of someone else's engine. Which indeed has certain advantages.

But the idea that it was done purely to create the greatest browser ever known to man or whatever is nonsense.

The question now for realists is what should happen going forward, as I don't believe Opera is going to turn back to Presto.

Can you give an estimate of how much such extensions would slow down the browser and clog the memory, since speed seems to be what Opera Next is supposed to offer in place of everything it used to offer?

Once you install an extension you can go to Developer Tools (I think you have enable them under More Tools first) and run Task Manager. This will tell you how much memory and other resources it is currently using. It also gives you the process ID which you can use to look at it using Windows' Task Manager if you want more detail.

Let's celebrate a few things in the new Opera. And for one, isn't it also enlightened self interest to do just that? If we focus on some of the good (and really, it is there just try to see, look, be fair, instead of always viewing the glass half empty, some of the lurkers, and others passing by, may sense positivity and vibrancy here, and think to give the new Opera a try.

I AM giving it a try, and agree that it has some advantages. I just don't think Stash and Discover are among them.

But it is also lacking in many ways, and glossing over all the (obvious) shortcomings is not "fair" either. It's not in one's "enlightened self interest" to pretend everything is great when some key features (IMO) have been dropped.

Why can't we express that there are things missing that we'd like back without every point we make being argued?

It's a work in progress. Does every feature added with subsequent releases have to be "new" to be considered worthwhile when there is no shortage of "old" features missing that can still be implemented in the new engine and are actually useful to some of us?