Mapquest.com works in Firefox on win10Pro but not win10Home
Does it work for you? What about other browsers, do thney use the same Javascript script?
Error message:
Application error: a client-side exception has occurred (see the browser console for more information).
(I couldn't actually find the entry in the console but since it worked
on the other computer, I stopped trying.)
Not only that 200 Ruth Lane, Centreville Md is found on both MapquestNow I'm on Linux but it worked for me, I mapped a route. Mozilla Firefox 132.0.1
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
Mapquest.com works in Firefox on win10Pro but not win10Home
Does it work for you? What about other browsers, do thney use the same Javascript script?
Error message:
Application error: a client-side exception has occurred (see the browser console for more information).
(I couldn't actually find the entry in the console but since it worked
on the other computer, I stopped trying.)
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
On 11/27/2024 1:58 PM, micky wrote:
Mapquest.com works in Firefox on win10Pro but not win10Home
Does it work for you?  What about other browsers, do thney use the same >> Javascript script?
Error message:
Application error: a client-side exception has occurred (see the browser
console for more information).
(I couldn't actually find the entry in the console but since it worked
on the other computer, I stopped trying.)
Not only that  200 Ruth Lane, Centreville Md is found on both Mapquest
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
I believe the website works as long as your browser has WebGL enabled.
For Firefox, that can only be changed in about:config.
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
Not only that 200 Ruth Lane, Centreville Md is found on both MapquestMapquest works on Win11 and Win10 Home (and also Pro)
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
Google Maps does not show the Ruth Lane, but it does pin the location
where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >presence - i.e. not shown even though it does exist).
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com>
wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both MapquestMapquest works on Win11 and Win10 Home (and also Pro)
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
Google Maps does not show the Ruth Lane, but it does pin the location
where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be
believed) label an access way as Ruth Lane... but it's shown to be
*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
The street-view display is totally out-to-lunch.
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 15:45:56 -0800, Nobody ><jock@soccer.com> wrote:
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> >>wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest >>>> and Google maps, but google doesn't show the whole driveway, most ofMapquest works on Win11 and Win10 Home (and also Pro)
which is under the trees, and it doesn't have a street named Ruth Lane. >>>> Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
Google Maps does not show the Ruth Lane, but it does pin the location >>>where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>>presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be >>believed) label an access way as Ruth Lane... but it's shown to be
*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
You're right. I didn't notice that. And it's not just Mapquest that
says it's the wrong street.
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 15:45:56 -0800, Nobody <jock@soccer.com> wrote:
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> >> wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest >>>> and Google maps, but google doesn't show the whole driveway, most ofMapquest works on Win11 and Win10 Home (and also Pro)
which is under the trees, and it doesn't have a street named Ruth Lane. >>>> Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
Google Maps does not show the Ruth Lane, but it does pin the location
where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>> presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be
believed) label an access way as Ruth Lane... but it's shown to be
*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
You're right. I didn't notice that. And it's not just Mapquest that
says it's the wrong street. Google does too by marking the house as
more than one street down. I'm surprised that anyone who went to the trouble to get his driveway turned into a street and named after him has
not contacted google to fix this. Because it is someone whose last name
is Ruth who lives there. --- Mapquest doesn't name the road/driveway
that Google calls Ruth. BTW, this was just a BTW for me. My real
question had been why it iddn't work in one computer and I haven't had
time to try what Allan said.
On Thu, 28 Nov 2024 19:25:04 -0500, micky <NONONOmisc07@fmguy.com>
wrote:
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 15:45:56 -0800, Nobody >><jock@soccer.com> wrote:
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> >>>wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest >>>>> and Google maps, but google doesn't show the whole driveway, most of >>>>> which is under the trees, and it doesn't have a street named Ruth Lane. >>>>> Even though it knows where the house is. Not surprisingly, when you >>>>> know who lives there, it's the only house on that street.Mapquest works on Win11 and Win10 Home (and also Pro)
Google Maps does not show the Ruth Lane, but it does pin the location >>>>where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>>>presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be >>>believed) label an access way as Ruth Lane... but it's shown to be >>>*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
You're right. I didn't notice that. And it's not just Mapquest that
says it's the wrong street.
Er...
Do you personally know from visiting where *exactly* Ruth Lane is
*actually* located?
You grumble about inconsistencies... but don't tell the world which is >ironclad correct?
MapQuest *appears* to have the correct locale for Ruth Lane... and
same for 200. Googly agrees (as far as) where 200 Ruthy is
positioned.
It's Googlee Maps which has mis-labelled something to the north of
Browning Ln.
But as I suggested to you in my reply on <a.c.s.firefox>, why not take
Googly up on their offer to accept corrections?
This is another of your micky mouse conundrums which could be solved
through your own homework.
On Thu, 11/28/2024 7:25 PM, micky wrote:
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 15:45:56 -0800, Nobody
<jock@soccer.com> wrote:
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com>
wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest >>>>> and Google maps, but google doesn't show the whole driveway, most of >>>>> which is under the trees, and it doesn't have a street named Ruth Lane. >>>>> Even though it knows where the house is. Not surprisingly, when you >>>>> know who lives there, it's the only house on that street.Mapquest works on Win11 and Win10 Home (and also Pro)
Google Maps does not show the Ruth Lane, but it does pin the location
where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>>> presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be
believed) label an access way as Ruth Lane... but it's shown to be
*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
You're right. I didn't notice that. And it's not just Mapquest that
says it's the wrong street. Google does too by marking the house as
more than one street down. I'm surprised that anyone who went to the
trouble to get his driveway turned into a street and named after him has
not contacted google to fix this. Because it is someone whose last name
is Ruth who lives there. --- Mapquest doesn't name the road/driveway
that Google calls Ruth. BTW, this was just a BTW for me. My real
question had been why it iddn't work in one computer and I haven't had
time to try what Allan said.
You can tell what is wrong, because Google did not drive their car
up Ruth Lane. Google does not recognize that as a public street.
If "Ruth Lane" had a municipal sign on the intersection, with the
words "Ruth Lane" on it, the driver might have ventured there.
Paul
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 23:47:19 -0500, Paul <nospam@needed.invalid> wrote:
On Thu, 11/28/2024 7:25 PM, micky wrote:
In alt.comp.os.windows-10, on Thu, 28 Nov 2024 15:45:56 -0800, Nobody
<jock@soccer.com> wrote:
On Wed, 27 Nov 2024 13:46:49 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com>
wrote:
micky wrote on 11/27/24 12:58 PM:
Mapquest.com works in Firefox on win10Pro but not win10Home
<cut that out>
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest >>>>>> and Google maps, but google doesn't show the whole driveway, most of >>>>>> which is under the trees, and it doesn't have a street named Ruth Lane. >>>>>> Even though it knows where the house is. Not surprisingly, when you >>>>>> know who lives there, it's the only house on that street.Mapquest works on Win11 and Win10 Home (and also Pro)
Google Maps does not show the Ruth Lane, but it does pin the location >>>>> where Ruth Lane exists(i.e. Google maps hasn't been coded for Ruth Lane's >>>>> presence - i.e. not shown even though it does exist).
Actually, Google Maps DOES (albeit incorrectly if MapQuest is to be
believed) label an access way as Ruth Lane... but it's shown to be
*north* of Browning Ln... not *south*... which is where that house in
the trees is (supposedly correctly) identified by Googly Maps as 200
Ruth Ln.
You're right. I didn't notice that. And it's not just Mapquest that
says it's the wrong street. Google does too by marking the house as
more than one street down. I'm surprised that anyone who went to the
trouble to get his driveway turned into a street and named after him has >>> not contacted google to fix this. Because it is someone whose last name >>> is Ruth who lives there. --- Mapquest doesn't name the road/driveway
that Google calls Ruth. BTW, this was just a BTW for me. My real
question had been why it iddn't work in one computer and I haven't had
time to try what Allan said.
You can tell what is wrong, because Google did not drive their car
up Ruth Lane. Google does not recognize that as a public street.
If "Ruth Lane" had a municipal sign on the intersection, with the
words "Ruth Lane" on it, the driver might have ventured there.
I'm surprised Mr. Ruth didn't get a sign put up.
For some reason I don't know, Maryland, or Baltimore County, has put up
blue street signs for privately owned streets (even those owned by HOA's
for example) and kept the green ones for publicly owned streets. But
our street does look like a street, not a driveway, and the google
street view guy has photographed it at least once.
On 11/27/2024 1:58 PM, micky wrote:
Mapquest.com works in Firefox on win10Pro but not win10Home
Does it work for you? What about other browsers, do thney use the same
Javascript script?
Error message:
Application error: a client-side exception has occurred (see the browser
console for more information).
(I couldn't actually find the entry in the console but since it worked
on the other computer, I stopped trying.)
Not only that 200 Ruth Lane, Centreville Md is found on both Mapquest
and Google maps, but google doesn't show the whole driveway, most of
which is under the trees, and it doesn't have a street named Ruth Lane.
Even though it knows where the house is. Not surprisingly, when you
know who lives there, it's the only house on that street.
I believe the website works as long as your browser has WebGL enabled.
For Firefox, that can only be changed in about:config.
In alt.comp.software.firefox, on Wed, 27 Nov 2024 16:11:14 -0600, Allan Higdon <allanh@vivaldi.net> wrote:
I believe the website works as long as your browser has WebGL enabled.
For Firefox, that can only be changed in about:config.
Well, on the computer where Mapquest did not work, in Firefox,
there are about 65 settings involving WebGL,
7 of which start with webgl.enable
5 of which are true and
2 of which are false
draft-extensions and Is this one it?
priveleged extensions Is this one it?
and 4 of wh ich start with webgl.disable
1 of which is true
fail-if-major-performance-caveat Is this one it?
and
3 of which are false
and 1 of which starts with webgl.disabled which is marked false.
There is also webgl.dxgl.enabled which is marked true.
There are 17 uses of the letters able. Above, I've only accounted for
13. The remaining 4 are:
webgl.force-enabled is false Is this one it?
2 more disabled items are false
(and 1 use of able is in acceptable)
So it is mostly enabled. Do the exceptions ring any bells?
Under Show only modified, there are none for all of webgl.
MAYBE MORE IMPORTANT IS THAT in the other computer all the items using
"able" are the same. A rare problem that a page won't work. Not sure
if it's worth more effort.
On Fri, 29 Nov 2024 10:38:31 -0600, micky <NONONOmisc07@fmguy.com> wrote:
In alt.comp.software.firefox, on Wed, 27 Nov 2024 16:11:14 -0600, Allan
Higdon <allanh@vivaldi.net> wrote:
I believe the website works as long as your browser has WebGL enabled.
For Firefox, that can only be changed in about:config.
Well, on the computer where Mapquest did not work, in Firefox,
there are about 65 settings involving WebGL,
7 of which start with webgl.enable
5 of which are true and
2 of which are false
draft-extensions and Is this one it?
priveleged extensions Is this one it?
and 4 of wh ich start with webgl.disable
1 of which is true
fail-if-major-performance-caveat Is this one it?
and
3 of which are false
and 1 of which starts with webgl.disabled which is marked false.
There is also webgl.dxgl.enabled which is marked true.
There are 17 uses of the letters able. Above, I've only accounted for
13. The remaining 4 are:
webgl.force-enabled is false Is this one it?
2 more disabled items are false
(and 1 use of able is in acceptable)
So it is mostly enabled. Do the exceptions ring any bells?
Under Show only modified, there are none for all of webgl.
MAYBE MORE IMPORTANT IS THAT in the other computer all the items using
"able" are the same. A rare problem that a page won't work. Not sure
if it's worth more effort.
I did see the same error message in my browser for Mapquest, if WebGL was disabled.
If none of the WebGL settings in your browser have been modified, that wasn't the problem.
In alt.comp.os.windows-10, on Fri, 29 Nov 2024 14:32:57 -0600, "Allan
Higdon" <allanh@vivaldi.net> wrote:
On Fri, 29 Nov 2024 10:38:31 -0600, micky <NONONOmisc07@fmguy.com> wrote:
In alt.comp.software.firefox, on Wed, 27 Nov 2024 16:11:14 -0600, Allan
Higdon <allanh@vivaldi.net> wrote:
I believe the website works as long as your browser has WebGL enabled. >>>> For Firefox, that can only be changed in about:config.
Well, on the computer where Mapquest did not work, in Firefox,
there are about 65 settings involving WebGL,
7 of which start with webgl.enable
5 of which are true and
2 of which are false
draft-extensions and Is this one it?
priveleged extensions Is this one it?
and 4 of wh ich start with webgl.disable
1 of which is true
fail-if-major-performance-caveat Is this one it?
and
3 of which are false
and 1 of which starts with webgl.disabled which is marked false.
There is also webgl.dxgl.enabled which is marked true.
There are 17 uses of the letters able. Above, I've only accounted for
13. The remaining 4 are:
webgl.force-enabled is false Is this one it?
2 more disabled items are false
(and 1 use of able is in acceptable)
So it is mostly enabled. Do the exceptions ring any bells?
Under Show only modified, there are none for all of webgl.
MAYBE MORE IMPORTANT IS THAT in the other computer all the items using
"able" are the same. A rare problem that a page won't work. Not sure
if it's worth more effort.
I did see the same error message in my browser for Mapquest, if WebGL was disabled.
If none of the WebGL settings in your browser have been modified, that wasn't the problem.
I'm tired of writing to Google and Microsoft. I think I will send this
one to Rod Serling.
On Fri, 11/29/2024 11:12 PM, micky wrote:
In alt.comp.os.windows-10, on Fri, 29 Nov 2024 14:32:57 -0600, "Allan
Higdon" <allanh@vivaldi.net> wrote:
On Fri, 29 Nov 2024 10:38:31 -0600, micky <NONONOmisc07@fmguy.com> wrote: >>>
In alt.comp.software.firefox, on Wed, 27 Nov 2024 16:11:14 -0600, Allan >>>> Higdon <allanh@vivaldi.net> wrote:
I believe the website works as long as your browser has WebGL enabled. >>>>> For Firefox, that can only be changed in about:config.
Well, on the computer where Mapquest did not work, in Firefox,
there are about 65 settings involving WebGL,
7 of which start with webgl.enable
5 of which are true and
2 of which are false
draft-extensions and Is this one it?
priveleged extensions Is this one it?
and 4 of wh ich start with webgl.disable
1 of which is true
fail-if-major-performance-caveat Is this one it?
and
3 of which are false
and 1 of which starts with webgl.disabled which is marked false.
There is also webgl.dxgl.enabled which is marked true.
There are 17 uses of the letters able. Above, I've only accounted for >>>> 13. The remaining 4 are:
webgl.force-enabled is false Is this one it?
2 more disabled items are false
(and 1 use of able is in acceptable)
So it is mostly enabled. Do the exceptions ring any bells?
Under Show only modified, there are none for all of webgl.
MAYBE MORE IMPORTANT IS THAT in the other computer all the items using >>>> "able" are the same. A rare problem that a page won't work. Not sure >>>> if it's worth more effort.
I did see the same error message in my browser for Mapquest, if WebGL was disabled.
If none of the WebGL settings in your browser have been modified, that wasn't the problem.
I'm tired of writing to Google and Microsoft. I think I will send this
one to Rod Serling.
The Ruth Lane does appear to be in another dimension.
The Ruth Lane exists, it's just the house is not on a road,
which doesn't make much sense.
In the normal Google Map, you can see we need to drive down that paved >surface and then turn a bit left, to get to the building with the dot.
Yet, the Ruth Lane itself is further up the map.
When you're in Google Map again, drive left in the map
and drive down Browning Lane until you get back to Dulin.
then drive up Dulin to Ruth.
[Picture]
https://i.postimg.cc/vH3d27nx/twilight-zone-ruth-lane.gif
If that's going on, then there must be a problem for courier
companies to deliver there.
Paul
In alt.comp.os.windows-10, on Sat, 30 Nov 2024 02:25:06 -0500, Paul ><nospam@needed.invalid> wrote:
On Fri, 11/29/2024 11:12 PM, micky wrote:
In alt.comp.os.windows-10, on Fri, 29 Nov 2024 14:32:57 -0600, "Allan
Higdon" <allanh@vivaldi.net> wrote:
On Fri, 29 Nov 2024 10:38:31 -0600, micky <NONONOmisc07@fmguy.com> wrote: >>>>
In alt.comp.software.firefox, on Wed, 27 Nov 2024 16:11:14 -0600, Allan >>>>> Higdon <allanh@vivaldi.net> wrote:
I believe the website works as long as your browser has WebGL enabled. >>>>>> For Firefox, that can only be changed in about:config.
Well, on the computer where Mapquest did not work, in Firefox,
there are about 65 settings involving WebGL,
7 of which start with webgl.enable
5 of which are true and
2 of which are false
draft-extensions and Is this one it?
priveleged extensions Is this one it?
and 4 of wh ich start with webgl.disable
1 of which is true
fail-if-major-performance-caveat Is this one it?
and
3 of which are false
and 1 of which starts with webgl.disabled which is marked false.
There is also webgl.dxgl.enabled which is marked true.
There are 17 uses of the letters able. Above, I've only accounted for >>>>> 13. The remaining 4 are:
webgl.force-enabled is false Is this one it?
2 more disabled items are false
(and 1 use of able is in acceptable)
So it is mostly enabled. Do the exceptions ring any bells?
Under Show only modified, there are none for all of webgl.
MAYBE MORE IMPORTANT IS THAT in the other computer all the items using >>>>> "able" are the same. A rare problem that a page won't work. Not sure >>>>> if it's worth more effort.
I did see the same error message in my browser for Mapquest, if WebGL was disabled.
If none of the WebGL settings in your browser have been modified, that wasn't the problem.
I'm tired of writing to Google and Microsoft. I think I will send this
one to Rod Serling.
The Ruth Lane does appear to be in another dimension.
The Ruth Lane exists, it's just the house is not on a road,
which doesn't make much sense.
PaulRod is busy right now, so it's good that you posted on the thread that
will not die.
Earlier, I wanted to try a 3rd map program but couldn't remember other
names. But today I went whole hog.
I tried open map,
Now OpenStreetMap (bottom) renames what the previous two label
*Browning Lane* as its choice!
As I asked before, do you, micky, know with ironclad certainty *where*
this house physically exists?
In alt.comp.os.windows-10, on Sat, 30 Nov 2024 14:29:36 -0800, Nobody <jock@soccer.com> wrote:
Now OpenStreetMap (bottom) renames what the previous two label
*Browning Lane* as its choice!
As I asked before, do you, micky, know with ironclad certainty *where*
this house physically exists?
This is just prep. No, I don't know with ironclad certainty where it
is, but before our invasion of Centreville begins, military intelligence
will have all that information.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 508 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 217:35:02 |
| Calls: | 9,974 |
| Calls today: | 5 |
| Files: | 13,831 |
| Messages: | 6,358,556 |
