FF 19 is Available

[Peter Taylor]

FYI
--
Peter Taylor

[Ant]

On 2/19/2013 8:52 AM PT, Peter Taylor typed:

> FYI

http://www.mozilla.org/en-US/firefox/19.0/releasenotes/ as well. ;)
--
"If I find one beer can in that car, it's over!" --Red; "And no donuts
either! Ants!" --Kitty from That '70s Show pilot
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.

[Keith Nuttle]

One of the new features the PDF viewer seems to have problem on Windows
XP SP3. I am running it on an Intel dual core 1.3 mh processor 1.5gb
ram, and about 40 gb free on my hard drive.

The extension are Quicknote, TableToo2, Microsoft .Net Assistant, Garmin
Communicator, Download Them all, Copy to word perfect, and Clippings.

Plugins are
Alterna TIFF 1.9.3.1
Garmin Update 4.0.4.0
Google Earth 6/2/0.5788
Google Update 1.3.21.123
Java Platform and toolKit 10..13.2.20
McAfee Security Center 12.1.231.0
MS media player plugin 1.0.0.8
Quicktime 7.7.3.0
Shockwave Flash 11.6.602.168

Before updating everything was work fine.

When I accessed the first PDF, the viewer locked up the system as I was
trying to navigate the PDF.

I restarted and disabled the Adobe Plug in. While it seemed to run
better initially, I got a script error. It eventually locked the whole
program and it had to be terminated from the system.


What am I doing wrong?

If necessary how do I disable the viewer?

[WaltS]

Not Restarting with Add-ons Disabled is one thing I can think of that
you are doing wrong.

Not providing a link to the problem PDF is another, and maybe not
starting a new thread.

To disable the built-in PDF Viewer toggle "pdfjs.disabled" in about:config.

--
Fedora 18.0 (64-bit) KDE 4.9.5
Thunderbird Release
Are they out yet?

[Keith Nuttle]

I did not restart with the addons disabled, as they were working in
18.0.2 perhapse I should have

I tried this with several PDFs from my hard drive, and have gone to
several other online sites that I know have PDF files, and tried several
of them. It was not one specific file but a general problem with PDF's.
These PDF were both image and text PDF's

Thanks for the config line to disable the PDF viewer. I will use it if
I cannot find a solutions


This is the first time in many version when something did not work with FF.

[goodwin]

On 02/19/2013 02:05 PM, Keith Nuttle wrote:
> On 2/19/2013 3:57 PM, WaltS wrote:
>> On 02/19/2013 03:48 PM, Keith Nuttle wrote:
>>> One of the new features the PDF viewer seems to have problem on Windows
>>> XP SP3. I am running it on an Intel dual core 1.3 mh processor 1.5gb
>>> ram, and about 40 gb free on my hard drive.
>>>
>>> The extension are Quicknote, TableToo2, Microsoft .Net Assistant, Garmin
>>> Communicator, Download Them all, Copy to word perfect, and Clippings.
>>>
>>> Plugins are
>>> Alterna TIFF 1.9.3.1
>>> Garmin Update 4.0.4.0
>>> Google Earth 6/2/0.5788
>>> Google Update 1.3.21.123
>>> Java Platform and toolKit 10..13.2.20
>>> McAfee Security Center 12.1.231.0
>>> MS media player plugin 1.0.0.8
>>> Quicktime 7.7.3.0
>>> Shockwave Flash 11.6.602.168
>>>
>>> Before updating everything was work fine.
>>>
>>> When I accessed the first PDF, the viewer locked up the system as I was
>>> trying to navigate the PDF.
>>>
>>> I restarted and disabled the Adobe Plug in. While it seemed to run
>>> better initially, I got a script error. It eventually locked the whole
>>> program and it had to be terminated from the system.
>>>

Until you sort it out, change your preference to open outside FF, as
Walt says. You didn't list Adobe Reader in your plugins - vers up to date?

>>>
>>> What am I doing wrong?

>>>
>>> If necessary how do I disable the viewer?
>>>
>>
>> Not Restarting with Add-ons Disabled is one thing I can think of that
>> you are doing wrong.
>>
>> Not providing a link to the problem PDF is another, and maybe not
>> starting a new thread.
>>
>> To disable the built-in PDF Viewer toggle "pdfjs.disabled" in
>> about:config.
>>
>
> I did not restart with the addons disabled, as they were working in
> 18.0.2 perhapse I should have
>
> I tried this with several PDFs from my hard drive, and have gone to
> several other online sites that I know have PDF files, and tried several
> of them. It was not one specific file but a general problem with PDF's.
> These PDF were both image and text PDF's
>

I believe .pdfs are considered images to most computers and to all
printers. I've never heard of a text .pdf but I'm not an expert with them

[Keith Nuttle]

Sorry I have the latest Adobe Reader 11.0.136

I have been using it tonight with the Adobe Reader disable. While I
have not run into any PDF, FF19 seems to be working well but definitely
slower than 18.

As for differences in PDF files, those with images of documents can be
viewed as those with text. In fact if they are the same document, you
will not see any difference. To see the difference, create a document
in a word processor and print to a PDF and then Print the same document
to paper, scan it, and create a PDF. With the Text PDF, you can copy
the text and highlight the individual lines. With the Image PDF you can
copy part of the image and paste it as an image, but you can not copy
the text in the image. You can not highlight the image PDF either.

[goodwin]

On 02/19/2013 07:11 PM, Keith Nuttle wrote:

<snip>

> As for differences in PDF files, those with images of documents can be
> viewed as those with text. In fact if they are the same document, you
> will not see any difference. To see the difference, create a document
> in a word processor and print to a PDF and then Print the same document
> to paper, scan it, and create a PDF.

er, ? and?

[Miles]

* Peter Taylor wrote, On 19-Feb-13 23:52:
> FYI
>

Thanks, however this is the 1st time I will not upgrade -- in the past
I usually waited for V x.0.0.2 or .3 before going ahead in order to
all extension updates. Now since Mozilla refuses to or for some
reason cannot provide info as to which extensions will be inoperative,
I no longer update.

However, quick to point out that this morning I did update TB from
17.0.2 to 17.0.3 since that security update showed little if anything
to fear. And as it turned out, all 26 extensions in use are OK, as
are the themes and plugins.
Miles

[goodwin]

Is there a reason for this post?

[Cal Tinson]

On 2/19/2013 3:57 PM eastern, WaltS wrote:

> To disable the built-in PDF Viewer toggle "pdfjs.disabled" in about:config.

Or go to Tools, Options, Applications, Portable Document Format (PDF) to
choose what you want to use (Foxit here).

[Miles]

* goodwin wrote, On 20-Feb-13 13:37:

The op said version 19 was available and I thought it appropriate to
supply fair warning for those who might need it after the fact as
occurred to me a few times in the past. And it connects to another
thread wherein several posters argued the fate of not being able to
check prior to updating.
Miles

[Bill Braun]

Minor version updates are not the only ones that address security
concerns. If you do not update to version 18.0, for example, you won't
receive the security updates contained in 18.0.x. Likewise for 19.0.x,
20.0.x, etc.

You are in effect freezing the security of FF at 17.0.3.

Bill

[Frank]

On 2/19/2013 11:52 AM, Peter Taylor wrote:
> FYI

Wonder when they update Waterfox?

Just started trying it and saw no differences except, now with FF 19,
pdf viewers are different.

[J. P. Gilliver (John)]

In message <FZednbSMdegA-LnM...@mozilla.org>, goodwin

Are you trolling? You snipped the rest of Keith's paragraph:

"With the Text PDF, you can copy the text and highlight the individual
lines. With the Image PDF you can copy part of the image and paste it
as an image, but you can not copy the text in the image. You can not
highlight the image PDF either."

(Personally, I've never seen the point of picture PDFs - or, at least,
of scanners producing them rather than any other picture format.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

What's awful about weird views is not the views. It's the intolerance. If
someone wants to worship the Duke of Edinburgh or a pineapple, fine. But don't
kill me if I don't agree. - Tim Rice, Radio Times 15-21 October 2011.

[Chris Ilias]

In case it wasn't clear in the previous thread you started on the
subject, Firefox defaults to assuming your extensions are compatible.
It's been like that for over a year.
For more info, visit
<http://brian.kingsonline.net/talk/2012/02/compatible-by-default-and-the-add-ons-compatibility-reporter/>.

--
Chris Ilias <http://ilias.ca>
Mailing list/Newsgroup moderator

[Chris Ilias]

Mozilla does not make Waterfox, so they would not be the ones to update
it. If you want to know if/when Waterfox is updated, the you should be
able to get an answer from Waterfox support, not here.
<http://www.waterfoxproject.org/support.php>

[Frank]

On 2/20/2013 6:46 PM, Chris Ilias wrote:
> On 2013-02-20 3:11 PM, Frank wrote:
>> On 2/19/2013 11:52 AM, Peter Taylor wrote:
>>> FYI
>>
>> Wonder when they update Waterfox?
>>
>> Just started trying it and saw no differences except, now with FF 19,
>> pdf viewers are different.
>
> Mozilla does not make Waterfox, so they would not be the ones to update
> it. If you want to know if/when Waterfox is updated, the you should be
> able to get an answer from Waterfox support, not here.
> <http://www.waterfoxproject.org/support.php>
>

Thanks. Someone mentioned it here and I thought it originated here.
Frank

[Keith Nuttle]

On 2/20/2013 6:21 PM, J. P. Gilliver (John) wrote:
> In message <FZednbSMdegA-LnM...@mozilla.org>, goodwin
> <jeff.g...@att.net> writes:
>> On 02/19/2013 07:11 PM, Keith Nuttle wrote:
>>
>> <snip>
>>
>>> As for differences in PDF files, those with images of documents can be
>>> viewed as those with text. In fact if they are the same document, you
>>> will not see any difference. To see the difference, create a document
>>> in a word processor and print to a PDF and then Print the same document
>>> to paper, scan it, and create a PDF.
>>
>> er, ? and?
>
> Are you trolling? You snipped the rest of Keith's paragraph:
>
> "With the Text PDF, you can copy the text and highlight the individual
> lines. With the Image PDF you can copy part of the image and paste it
> as an image, but you can not copy the text in the image. You can not
> highlight the image PDF either."
>
> (Personally, I've never seen the point of picture PDFs - or, at least,
> of scanners producing them rather than any other picture format.)

The point of scanned images as PDF is that they are easier to navigate.
In my case scanned images are not pictures but documents, like several
pages of old wills, deeds, and such.

With old documents the zoom ability of a PDF is very handy in
deciphering the handwritten text.

[WaltS]

On 02/21/2013 01:27 PM, Sailfish wrote:
> My bloviated meandering follows what NA graced us with on 2/21/2013 7:38 AM:

>> Definitely a problem with FF 19 and Adobe Reader 12, here's an example
>> of bad PDF rendering:
>>
>> http://www.bostonburgerco.com/wp-content/uploads/images/menu-original-boylston-outlines.pdf
>>
>> One can view the difference/problem via FF19 and then via AR12 directly.
>>
> Same here. It looks like the Fx PDF viewer can't handle watermarks
> correctly.
>


Same here. Looks like it can't.

Why didn't Mozilla test this before releasing it, some will whine. :)

--
Fedora 18.0 (64-bit) KDE 4.9.5

Thunderbird Daily
If we burn in hell, do we freeze in heaven?

[Pete]

More FYI:

In addition to the watermark problem, the FF Javascript/HTML5 pdf
renderer makes the fonts a bit fuzzier and doesn't work well with
fillable pdfs (although for the latter, it does give you a warning that
"This PDF document might not be displayed correctly)."

Any fillable form at irs.gov will show both problems, e.g.
http://www.irs.gov/pub/irs-pdf/f1040.pdf

I believe Mozilla already knows about both issues:

http://support.mozilla.org/en-US/questions/951243
https://bugzilla.mozilla.org/show_bug.cgi?id=739043

[PhillipJones]

Government PDF Forms are XFA or XML Based. I doubt seriously Mozilla
even considered XFA/XML based PDF when the created the pdf.js.

--
Phillip M. Jones, C.E.T. "If it's Fixed, Don't Break it"
http://www.phillipmjones.net mailto:pjon...@comcast.net

[Pete]

Here's a non-government fillable PDF form. The font rendering is
crisper than the IRS forms, but it's still not fillable using the pdf.js
renderer -->
http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf

[Ron Hunter]

Well, it worked for me using FF 20 beta1.

[Rob]

PhillipJones <pjon...@comcast.net> wrote:
> Government PDF Forms are XFA or XML Based. I doubt seriously Mozilla
> even considered XFA/XML based PDF when the created the pdf.js.

The problem with making a PDF reader is that there are so many
different features that are potentially to be supported.
There have been several "competitor" PDF viewers that started as
small and snappy and secure, and after enough features had been
added to make them into a real alternative for Adobe Reader they
became the smae kind of insecure slow monsters as Adobe Reader itself.

Either the same will happen to the js reader, or it will be unable
to render a (growing) portion of PDF documents, and it will be
a nuisance to users.

[»Q«]

On Sun, 24 Feb 2013 04:38:45 -0600
Rob <nom...@example.com> wrote:

> PhillipJones <pjon...@comcast.net> wrote:
> > Government PDF Forms are XFA or XML Based. I doubt seriously
> > Mozilla even considered XFA/XML based PDF when the created the
> > pdf.js.
>
> The problem with making a PDF reader is that there are so many
> different features that are potentially to be supported.

There are a couple of ways to make pdfs with fillable forms, and of
course Phillip is wrong about Mozilla not considering them.

"Acroforms" are part of the pdf standard; Mozilla can't handle them
now, but they'd like to.

XFA (XML Form Architecture) is not part of the pdf standard; it's a
proprietary extension of Adobe's. The ISO working group which
maintains the pdf standard has urged Adobe to submit it so that it
could be part of the standard, but to no avail. Mozilla is much less
likely to devote resources to supporting proprietary stuff, though
they'd like to be able to support gubment forms because a lot of people
need them.

[Ron Hunter]

I took the example given by Phillip, and displayed it on FF 20 beta, and
filled in the form, and printed it. No problem at all. So, if it isn't
in 19, it's coming.

[Ron Hunter]

On 2/24/2013 2:11 PM, Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on
> 2/24/2013 1:30 AM:

>> On 2/24/2013 12:09 AM, Pete wrote:
>

> [snip /]

>>>
>>> Here's a non-government fillable PDF form. The font rendering is
>>> crisper than the IRS forms, but it's still not fillable using the pdf.js
>>> renderer -->
>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>
>> Well, it worked for me using FF 20 beta1.
>>

> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>
Worked fine here. You have to put the cursor in the firs field, and click.

[WaltS]

Put my cursor in the first field, clicked, and form wouldn't fill for me
using Fx 20.0b1 or Fx 22.0a1.

--
Fedora 18.0 (64-bit) KDE 4.9.5

Thunderbird Release

[PhillipJones]

I don't care that much about XFA/XML Form Fill out. All Government
Federal, State PDF Forms are XFA/XML. I just want to be able to fill out
standard PDF Forms. and have the ability to click the home button on
PDf and go back to Home Page.

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on
> 2/24/2013 1:30 AM:

>> On 2/24/2013 12:09 AM, Pete wrote:
>

> [snip /]

>>>
>>> Here's a non-government fillable PDF form. The font rendering is
>>> crisper than the IRS forms, but it's still not fillable using the pdf.js
>>> renderer -->
>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>
>> Well, it worked for me using FF 20 beta1.
>>

> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>

Didn't exactly display correctl and would fill out

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what »Q« graced us with on 2/24/2013
> 8:48 AM:

> Chrome handles it well so I hope Fx eventually finds a non-bloaty way to
> do it as well, for my usage of PDFs, the fill-in capability is a minor
> limitation.
>
> Others mileage may vary
>
To effectively use my PDF's in My Website I can now only use Chrome I
was able to use them inan older version of PDFBrowser Plugin no longer
works. Seems like javascript button that go to websiteWeare blocked out.
IN FF that use to work.

[PhillipJones]

Put in first field.

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on

> 2/24/2013 12:33 PM:

> Yep, no love. I even restarted in safe-mode. You're using the Fx
> built-in pdfjs reader, yes?
>
Yes I tried the PDF.Js

[PhillipJones]

PhillipJones wrote:
> Sailfish wrote:
>> My bloviated meandering follows what Ron Hunter graced us with on
>> 2/24/2013 1:30 AM:
>>> On 2/24/2013 12:09 AM, Pete wrote:
>>
>> [snip /]
>>>>
>>>> Here's a non-government fillable PDF form. The font rendering is
>>>> crisper than the IRS forms, but it's still not fillable using the
>>>> pdf.js
>>>> renderer -->
>>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>>
>>>>
>>> Well, it worked for me using FF 20 beta1.
>>>
>> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>>

> Didn't exactly display correctly and wouldn't fill out
>
Sorry I mistyped I corrected above.

[PhillipJones]

PhillipJones wrote:
> Ron Hunter wrote:
>> On 2/24/2013 2:11 PM, Sailfish wrote:
>>> My bloviated meandering follows what Ron Hunter graced us with on
>>> 2/24/2013 1:30 AM:
>>>> On 2/24/2013 12:09 AM, Pete wrote:
>>>
>>> [snip /]
>>>>>
>>>>> Here's a non-government fillable PDF form. The font rendering is
>>>>> crisper than the IRS forms, but it's still not fillable using the
>>>>> pdf.js
>>>>> renderer -->
>>>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>>>
>>>>>
>>>>>
>>>> Well, it worked for me using FF 20 beta1.
>>>>
>>> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>>>
>> Worked fine here. You have to put the cursor in the firs field, and
>> click.
>>

> Clicked in first field.
>

Still wasn't able to fill in.

[PhillipJones]

IN my Website.

[Jay Garcia]

On 24.02.2013 15:09, WaltS wrote:

Worked here in 19 21 and 22 no problem. Did you follow directions?
Somehow clicking on a "key" will make the field change and can then type in.

--
Jay Garcia - www.ufaq.org - Netscape - Firefox - SeaMonkey - Thunderbird
Mozilla Contribute Coordinator Team - www.mozilla.org/contribute/
Mozilla Mozillian Member - www.mozillians.org
Mozilla Contributor Member - www.mozilla.org/credits/

[WaltS]

On 02/24/2013 07:43 PM, Jay Garcia wrote:
> On 24.02.2013 15:09, WaltS wrote:
>
> --- Original Message ---
>
>> On 02/24/2013 03:33 PM, Ron Hunter wrote:
>>> On 2/24/2013 2:11 PM, Sailfish wrote:
>>>> My bloviated meandering follows what Ron Hunter graced us with on
>>>> 2/24/2013 1:30 AM:
>>>>> On 2/24/2013 12:09 AM, Pete wrote:
>>>>
>>>> [snip /]
>>>>>>
>>>>>> Here's a non-government fillable PDF form. The font rendering is
>>>>>> crisper than the IRS forms, but it's still not fillable using the
>>>>>> pdf.js
>>>>>> renderer -->
>>>>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>>>>
>>>>>>
>>>>> Well, it worked for me using FF 20 beta1.
>>>>>
>>>> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>>>>
>>> Worked fine here. You have to put the cursor in the firs field,
>>> and click.
>>>
>>
>> Put my cursor in the first field, clicked, and form wouldn't fill for me
>> using Fx 20.0b1 or Fx 22.0a1.
>>
>
> Worked here in 19 21 and 22 no problem. Did you follow directions?
> Somehow clicking on a "key" will make the field change and can then type in.
>

All the directions are for Adobe Reader, and clicking a "key" does nothing.

Maybe it is only working in Windows, definitely doesn't in my Firefox on
Linux, using the new Firefox feature.

[Ron Hunter]

Perhaps something is getting in the way of it on your system.
Extensions? Settings? Or maybe it is like my wife's computer,
identical hardware, with the same Win7 release, but they work quite
differently.
At least, if it works for me, it probably works for others also.

[Ron Hunter]

On 2/24/2013 3:12 PM, Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on

> 2/24/2013 12:33 PM:

> Yep, no love. I even restarted in safe-mode. You're using the Fx
> built-in pdfjs reader, yes?
>

OOPS. Not on this computer. My mistake. Adobe Reader (latest version).

[PhillipJones]

Jay Garcia wrote:
> On 24.02.2013 15:09, WaltS wrote:
>
> --- Original Message ---
>
>> On 02/24/2013 03:33 PM, Ron Hunter wrote:
>>> On 2/24/2013 2:11 PM, Sailfish wrote:
>>>> My bloviated meandering follows what Ron Hunter graced us with on
>>>> 2/24/2013 1:30 AM:
>>>>> On 2/24/2013 12:09 AM, Pete wrote:
>>>>
>>>> [snip /]
>>>>>>
>>>>>> Here's a non-government fillable PDF form. The font rendering is
>>>>>> crisper than the IRS forms, but it's still not fillable using the
>>>>>> pdf.js
>>>>>> renderer -->
>>>>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>>>>
>>>>>>
>>>>> Well, it worked for me using FF 20 beta1.
>>>>>
>>>> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>>>>
>>> Worked fine here. You have to put the cursor in the firs field,
>>> and click.
>>>
>>
>> Put my cursor in the first field, clicked, and form wouldn't fill for me
>> using Fx 20.0b1 or Fx 22.0a1.
>>
>
> Worked here in 19 21 and 22 no problem. Did you follow directions?
> Somehow clicking on a "key" will make the field change and can then type in.
>

Yes I followed directions.

[PhillipJones]

Neither works on Mac as well. If you download and open in Reader sure it
will work.

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what PhillipJones graced us with on
> 2/24/2013 3:53 PM:

> Unfortunately, I'm not familiar with that plugin so I cannot speak to
> the problem(s) you're having with it. Have you tried the Adobe plugin?
>
Doesn't work in FireFx and adobe said they had no intention of making it
compatible with Gecko based Browsers.

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what PhillipJones graced us with on
> 2/24/2013 3:53 PM:

> Unfortunately, I'm not familiar with that plugin so I cannot speak to
> the problem(s) you're having with it. Have you tried the Adobe plugin?
>

here is a link to the PDFBrowser Plugin I refer to
http://www.schubert-it.com/pluginpdf/

[PhillipJones]

NO wonder. Disadvantage of using reader is that each time you access the
PDF it downs load a new Copy. If Reader would Open the file on line and
allow the fill out while on line I'd just switch over to reader.

[Ron Hunter]

On 2/24/2013 8:10 PM, Sailfish wrote:
> My bloviated meandering follows what Ron Hunter graced us with on

> 2/24/2013 5:26 PM:

> That would explain it :)
>
Another 'senior moment'. Been switching between the computers too much.

[Ron Hunter]

I am not sure I understand what you mean. I was online through the
download and fill out, and print, process. I wouldn't have noticed any
repeat of the download, though, as the file is very small.

[Jay Garcia]

On 24.02.2013 19:08, Sailfish wrote:

--- Original Message ---

> My bloviated meandering follows what Jay Garcia graced us with on
> 2/24/2013 4:43 PM:

>> On 24.02.2013 15:09, WaltS wrote:
>>
>> --- Original Message ---
>>
>>> On 02/24/2013 03:33 PM, Ron Hunter wrote:
>>>> On 2/24/2013 2:11 PM, Sailfish wrote:
>>>>> My bloviated meandering follows what Ron Hunter graced us with on
>>>>> 2/24/2013 1:30 AM:
>>>>>> On 2/24/2013 12:09 AM, Pete wrote:
>>>>> [snip /]
>>>>>>> Here's a non-government fillable PDF form. The font rendering is
>>>>>>> crisper than the IRS forms, but it's still not fillable using the
>>>>>>> pdf.js
>>>>>>> renderer -->
>>>>>>> http://www.thewebjockeys.com/TheWebJockeys/Fillable_PDF_Sample_from_TheWebJockeys_vC5.pdf
>>>>>>>
>>>>>>>
>>>>>> Well, it worked for me using FF 20 beta1.
>>>>>>
>>>>> It displays okay but I wasn't able to fill it in with Fx20.0b1.
>>>>>
>>>> Worked fine here. You have to put the cursor in the firs field,
>>>> and click.
>>>>
>>> Put my cursor in the first field, clicked, and form wouldn't fill for me
>>> using Fx 20.0b1 or Fx 22.0a1.
>>
>> Worked here in 19 21 and 22 no problem. Did you follow directions?
>> Somehow clicking on a "key" will make the field change and can then
>> type in.
>>

> Are you using the built-in Fx Firefox reader, pdfjs, or another PDF plugin?
>

Yes - Tools => Options => Applications => Adobe Acrobat Reader => (In
Firefox)

Double click any field and fill it in, no problem.

[pe...@never.here]

On Sun, 24 Feb 2013 19:59:09 -0500, WaltS <wls1...@REMOVEyahoo.com>
wrote:

Ubuntu 12.04 LTS FF V19 works if application set to "document viewer,
default" but not if set to "preview in FF" Form displays correctly and
info able to be entered in all the fields.
--
Pete

[PhillipJones]

Sailfish wrote:
> My bloviated meandering follows what PhillipJones graced us with on

> 2/24/2013 9:07 PM:

> Was that a recent announcement? I ask because their plugin was working
> for me until I decided to uninstall it after Fx supported pdfja.
>
It was an answer to me from an Adobe employee for Gecko based Browers on
Mac. The said in no uncertain terms they have no intention of ever
support Gecko Based Browsers on Mac.

[Sailfish]

My bloviated meandering follows what Jay Garcia graced us with on

2/25/2013 4:22 AM:

My setting is:

Tools => Options => Applications => Portable Document Format (PDF) =>
(Preview in Firefox)

When you view the PDF is the content area background a darkish grey?

--
Sailfish - Netscape Champion

Mozilla Contributor Member - www.mozilla.org/credits/

Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
Rare Mozilla Stuff: http://www.projectit.com/

[Jay Garcia]

Yes (Preview In Firefox) and yes, background is a charcoal color
(darkish grey).

Also tried again to fill in the form. A single click in the box doesn't
work but doing a dbl-click does and then able to fill in.

--
Jay Garcia - www.ufaq.org - Netscape - Firefox - SeaMonkey - Thunderbird
Mozilla Contribute Coordinator Team - www.mozilla.org/contribute/
Mozilla Mozillian Member - www.mozillians.org

[Ron Hunter]

Very strange. I set the computer to use the internal PDF display, and
the test form appeared, but when I double-clicked on a field, and tried
to type Ron, it rotated the page 90 degrees.
Tried again after reload, and same thing, but 90 degrees the OTHER
direction. Weird!

[pe...@never.here]

On Tue, 26 Feb 2013 16:30:21 -0600, Ron Hunter <rphu...@charter.net>
wrote:

>>
>>
>Very strange. I set the computer to use the internal PDF display, and
>the test form appeared, but when I double-clicked on a field, and tried
>to type Ron, it rotated the page 90 degrees.
>Tried again after reload, and same thing, but 90 degrees the OTHER
>direction. Weird!

Does that for me also. It's the only letter that has that effect.
Still can't enter anything into the boxes though.
--
Pete

[Sailfish]

My bloviated meandering follows what Sailfish graced us with on
2/21/2013 12:04 PM:
> My bloviated meandering follows what WaltS graced us with on 2/21/2013
> 10:49 AM:
>> On 02/21/2013 01:27 PM, Sailfish wrote:
>>> My bloviated meandering follows what NA graced us with on 2/21/2013
>>> 7:38 AM:
>>>> On 2/19/2013 3:48 PM EDT, Keith Nuttle wrote:
>>>>> One of the new features the PDF viewer seems to have problem on
>>>>> Windows
>>>>> XP SP3. I am running it on an Intel dual core 1.3 mh processor 1.5gb
>>>>> ram, and about 40 gb free on my hard drive.
>>>>>
>>>>> The extension are Quicknote, TableToo2, Microsoft .Net Assistant,
>>>>> Garmin
>>>>> Communicator, Download Them all, Copy to word perfect, and Clippings.
>>>>>
>>>>> Plugins are
>>>>> Alterna TIFF 1.9.3.1
>>>>> Garmin Update 4.0.4.0
>>>>> Google Earth 6/2/0.5788
>>>>> Google Update 1.3.21.123
>>>>> Java Platform and toolKit 10..13.2.20
>>>>> McAfee Security Center 12.1.231.0
>>>>> MS media player plugin 1.0.0.8
>>>>> Quicktime 7.7.3.0
>>>>> Shockwave Flash 11.6.602.168
>>>>>
>>>>> Before updating everything was work fine.
>>>>>
>>>>> When I accessed the first PDF, the viewer locked up the system as I
>>>>> was
>>>>> trying to navigate the PDF.
>>>>>
>>>>> I restarted and disabled the Adobe Plug in. While it seemed to run
>>>>> better initially, I got a script error. It eventually locked the
>>>>> whole
>>>>> program and it had to be terminated from the system.
>>>>>
>>>>>
>>>>> What am I doing wrong?
>>>>>
>>>>> If necessary how do I disable the viewer?
>>>>
>>>> Definitely a problem with FF 19 and Adobe Reader 12, here's an example
>>>> of bad PDF rendering:
>>>>
>>>> http://www.bostonburgerco.com/wp-content/uploads/images/menu-original-boylston-outlines.pdf
>>>>
>>>> One can view the difference/problem via FF19 and then via AR12
>>>> directly.
>>>>
>>> Same here. It looks like the Fx PDF viewer can't handle watermarks
>>> correctly.
>>
>> Same here. Looks like it can't.
>>
>> Why didn't Mozilla test this before releasing it, some will whine. :)
>>
> REF: https://bugzilla.mozilla.org/show_bug.cgi?id=843752
>
> Note: For tracing only, whining should remain here, not in bug report. :)
>
REF: https://bugzilla.mozilla.org/show_bug.cgi?id=843321

[excerpt quote=\"
WFM in current nightly(23).
\" /]

--
Sailfish - Netscape Champion

Mozilla Contributor Member - www.mozilla.org/credits/

[WaltS]

Let us hope they update Firefox 21 and 22 to Firefox 23's version of PDF
Viewer.

I can confirm it is fixed in 23, but still doesn't display correctly in 21.

I doubt they would roll out a 20.0.2 just for that fix.

--
openSUSE 12.3 (64-bit) KDE 4.10.0
Thunderbird Release
April is Jazz Appreciation Month
Quidditch World Cup VI is this weekend

[Sailfish]

My bloviated meandering follows what WaltS graced us with on 4/11/2013
6:06 PM:

Especially with the bug classified as,

*Importance*: P3 normal with 1 vote (vote)