Recent activity
Subscribe to this feed
Lech Deregowski replied on October 20, 2009 02:30 to the problem "about:ubiquity page does not work" in Mozilla:
In 0.5.4 we ran into a couple of snags with localizations and the way we included them. If I recall correctly a couple of them that were available had an error or two that caused all of the about pages to throw errors. Most of these have been fixed in the beta versions but I believe that a few locales in the current 0.5.4 release still have a slight problem.
Not to worry, this will be completely ironed out in the next release.
Lech Deregowski replied on October 07, 2009 17:43 to the question "Can I write an add-on specific for a country?" in Mozilla:
Start here: https://developer.mozilla.org/en/Loca... and see here https://developer.mozilla.org/en/Loca...
Lech Deregowski replied on September 28, 2009 19:56 to the problem "Ubiquity fonts looks fuzzy, colorful and not smooted, it's hard to read text." in Mozilla:
Well, Ubiquity is using a typical font selection just like any website would using CSS so nothing extraordinary is going on there. The fuzziness you're seeing is likely the result of white text on a dark background rendered by ClearType.
What I was hinting at was to switch ClearType rendering in for Standard rendering as fonts rendered at smaller sizes tend to be blurry and unreadable. Then, only characters that are bold or above a certain size will receive the proper antialiased treatment.
I can't blame you for pointing this out as an annoyance, but it's not something Ubiquity or Firefox can control with an absolute degree of certainty. ClearType on XP isn't exactly the best typeface rendering solution, while it does well in many areas it still manages to come up short in others. That's simply my opinion though.
Lech Deregowski replied on September 28, 2009 02:55 to the problem "Ubiquity fonts looks fuzzy, colorful and not smooted, it's hard to read text." in Mozilla:
Paul, this isn't anything Ubiquity or Firefox do specifically as the bulk of font rendering is handled by ClearType preferences in XP itself. This is why you're seeing what you believe to be fuzzy-looking fonts isn't limited to Ubiquity. If you don't like ClearType, there are options to turn it off and go back to "standard" font rendering.
A quick Google search produced this which will help you do just that: http://www.digitalsurvivors.com/archi...
A comment on the question "Digg comments look UGLY" in Mozilla:
They could have, but that still may not explain how, why or even if Ubiquity was causing the problem originally. – Lech Deregowski, on September 15, 2009 22:40
Lech Deregowski replied on September 15, 2009 19:17 to the question "Digg comments look UGLY" in Mozilla:
Hmmmm, I don't understand what in Ubiquity might be causing this. In fact Ubiquity shouldn't be rewriting, adding, or doing anything to diggs site or comments based on what I can tell. And what makes it even stranger is that I'm unable to reproduce this on any of the versions of Ubiquity running here :\
Lech Deregowski replied on September 15, 2009 19:12 to the problem "ctrl+space no longer opens command window in Ubiquity 0.5.5pre3..." in Mozilla:
Lech Deregowski replied on September 06, 2009 01:41 to the problem "Ubiquity will not add events to my google calendar properly" in Mozilla:
Odd, I'm not having this problem but then again I'm on Windows running 0.5.5pre7 and not using growl. What version of Ubiquity is everyone who has this problem using? 0.5.4?
You can see which version you're using if you open about:ubiquity in a tab or by going to tools > add-ons within Firefox. Any more info you can give us like which OS you're running and if Growl (or other notification service is installed) helps.
A comment on the problem "Ubiquity will not add events to my google calendar properly" in Mozilla:
OK, that's just a generic Firefox local file not found error, although I'm trying to understand what's triggering it... From what I can gather you're not invoking anything through Ubiquity so If it's bug19, it's probably trying to display a growl message. The contents of that message are unknown to me at the moment, but it's failing and then trying to display the bug19 error page and we're pointing it to it's old location somewhere.
I'm going to do some digging and see where that's being referenced and hopefully clear it up in the next version. What version of Ubiquity are you currently running at the moment? – Lech Deregowski, on September 06, 2009 01:20
Lech Deregowski replied on September 05, 2009 14:31 to the problem "Ubiquity will not add events to my google calendar properly" in Mozilla:
Is this still attempting to open up bug19warning.HTML and not .XHTML which is throwing the error?
If you could give me an example of the command you're using which causes this, I'll try to track it down and have it fixed in the next version. I though I found all instances of this but apparently not. It should be pointing to the updated xhtml instead of giving a not found error.
Lech Deregowski replied on September 04, 2009 00:08 to the question "How do you stop number rounding?" in Mozilla:
A comment on the idea "Ubiquity notifications are too ubiquitous" in Mozilla:
Alright, hopefully we'll have fixed this in an upcoming version. Thanks for being patient. :) – Lech Deregowski, on August 31, 2009 16:27
A comment on the question "Digg comments look UGLY" in Mozilla:
OK, well did you disable Ubiquity and attempt to view digg again to confirm whether or not it was causing the problem you were seeing? If it's not Ubiquity causing the problem I would suspect that it's probably something else. – Lech Deregowski, on August 31, 2009 16:25
A comment on the question "Digg comments look UGLY" in Mozilla:
Hmmm, are you sure it's Ubiquity causing what you're seeing and not possibly another add-on? Disable Ubiquity and see if the problem persists.
Most often when a site looks a bit messed up, it's often either the result of something on the server has changed and you have an old copy of the CSS or HTML still in your cache otherwise some other add-on which you may have installed could be attempting to rewrite the pages you're seeing. Alternately you could also have some userContent styles defined for digg.
Start the process of elimination by disabling Ubiquity and flushing just your cache for the moment then revisit digg to make sure the site displays normally. If it does, enable Ubiquity again and try what you were attempting to do with Ubiquity again. – Lech Deregowski, on August 30, 2009 15:35
Lech Deregowski replied on August 30, 2009 11:49 to the idea "Ubiquity notifications are too ubiquitous" in Mozilla:
Sorry about the late reply, Mr. Gunn...
I think what you're seeing over the regular growl messages are just Firefox toaster (systray-like) pop-ups. I've seen these whenever parser 2 is enabled but there are still parser 1 commands (they'll be marked on the right with a little red tag) enabled in the command list. Chances are these also double up and appear as growl messages as well (I don't use growl so I don't know) which can quickly become annoying.
If you're using parser 2, a good start would be to disable all of the parser 1 commands in your list. After which you should be able to restart Firefox and they should disappear. If that doesn't work, you can try to unsubscribe from those feeds to see if has any effect.
Personally, I ended up purging all parser 1 commands from my list as I too was getting those messages frequently enough to a point where I no longer wanted to see them. I would only recommend this if you're comfortable with losing all of those feeds.
On a side note, I know that there might be some growl-specific settings in the next version which should allow you to more finely tune and control some of the messages that are displayed. But since I don't use growl myself I couldn't tell you if it works or not. If you're daring enough you could grab one of the latest beta versions to give it a spin and perhaps give some feedback.
A comment on the question "Digg comments look UGLY" in Mozilla:
Did it fix the issue you were seeing? – Lech Deregowski, on August 30, 2009 11:30
Lech Deregowski replied on August 30, 2009 04:30 to the question "Digg comments look UGLY" in Mozilla:
I would suggest upgrading Ubiquity to the latest 0.5.x version to see if you get the same results as in Ubiquity 0.1.9. It's possible that the command is just older and hasn't received an update if anything on digg has changed since the digg command was last updated.
Also, I don't see your attached screen shot (then again I haven't used digg in quite some time either) so I don't know what it is that you're seeing exactly.
Lech Deregowski replied on August 25, 2009 03:14 to the problem "Herd is down" in Mozilla:
Herd has been down for a while and it's a known issue as the new herd is being built back up again. There's no real message currently indicating this, as such so it appears to be "up and running" even though it doesn't return anything worthwhile. I would suggest in the meantime we have a temporary page which reads something like: "We're out wrangling the herd at the moment and we'll be back shortly. Sorry for the inconvenience."
In the meantime, you can still use commands found in the wild until the Herd returns: https://wiki.mozilla.org/Labs/Ubiquit...
Lech Deregowski replied on August 23, 2009 21:39 to the idea "Ubiquity notifications are too ubiquitous" in Mozilla:
Yeah, Craig, I tend to agree with you somewhat as they did bug me too, but once you click the "don't remind me again" button you shouldn't see these messages again. There has been some discussion on how to better display this feature, but mostly I've learned to ignore it for now.
The idea is to keep them for new users who will likely benefit from the reminder, and probably less useful for you or I who have been using Ubiquity for a while. Although, striking a balance there without adding a pref is a bit difficult.
Back to the original topic though : Mr. Gunn, any ideas on what messages you're seeing?
Lech Deregowski replied on August 23, 2009 05:34 to the idea "Ubiquity notifications are too ubiquitous" in Mozilla:
| next » « previous |
Loading Profile...



