Jump to content

Search the Community

Showing results for tags 'chrome'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to PHP Freaks
    • Announcements
    • Introductions
  • PHP Coding
    • PHP Coding Help
    • Regex Help
    • Third Party Scripts
    • FAQ/Code Snippet Repository
  • SQL / Database
    • MySQL Help
    • PostgreSQL
    • Microsoft SQL - MSSQL
    • Other RDBMS and SQL dialects
  • Client Side
    • HTML Help
    • CSS Help
    • Javascript Help
    • Other
  • Applications and Frameworks
    • Applications
    • Frameworks
    • Other Libraries
  • Web Server Administration
    • PHP Installation and Configuration
    • Linux
    • Apache HTTP Server
    • Microsoft IIS
    • Other Web Server Software
  • Other
    • Application Design
    • Other Programming Languages
    • Editor Help (PhpStorm, VS Code, etc)
    • Website Critique
    • Beta Test Your Stuff!
  • Freelance, Contracts, Employment, etc.
    • Services Offered
    • Job Offerings
  • General Discussion
    • PHPFreaks.com Website Feedback
    • Miscellaneous

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Age


Donation Link

Found 6 results

  1. I have an iframe in a html or php site (tried both) and it works fine on Firefox and my mobile browsers. But Chrome behaves badly. The iframed php page contains a form and when I send it the whole iframe disapears. But it reapears when "painting it with my mouse". no cliks needed. just some mouseover/hovering. The whole iframe don't appear at once but small part of it. Therefor the "painting expirience". It is annoying because the visitor don't kmow to do this. Sorry, but i dont know how to explain this any better. the form is a domain lookup form (whois).
  2. I have a php application that serves pdf downloads. It works fine on all devices and browsers with one small but really annoying side-effect (edge-case for sure) When I look at my download logs anytime the download is triggered from Chrome on Android it is called twice! Bizarre behavior and I can't figure it out. Some background: The download is a pdf that get's created on the fly. All requests get processed through my index.php controller. I was serving the request with javascript via: window.open('export?file=something_to_inform_the_controller'); Works great in all browsers and devices but android chrome triggers this twice. So I got wise and though maybe a direct link would work better: <a target="_blank" href="http://mysite.com/export?file=abc123" download="file.pdf">DL link</a> or <a target="_blank" href="http://mysite.com/export?file=abc123">DL link</a> or <a target="_self" href="http://mysite.com/export?file=abc123" download="file.pdf">DL link</a> or <a target="_self" href="http://mysite.com/export?file=abc123">DL link</a> Nope, none of these flavors prevents android/chrome from double downloading. Then I researched my php header settings and tried: content-disposition: inline vs. content-disposition: attachment with no success Note, the download is logged when the controller processes the request for the download. I have duplicated download events for all downloads on android/chrome. It's strange that I have not found a solution online for this or maybe I'm overlooking something silly. Any ideas?
  3. <?PHP require("../fpdf/fpdf.php"); include("db.classes.php"); $g = new DB(); $g->connection(); class PDF extends FPDF { .....codes..... } $pdf = new PDF(); .....codes..... $pdf->SetFont('Arial','',14); $pdf->AddPage('L', 'Legal'); $pdf->SetXY(20,20); $pdf->image('../images/DCWD Watermark.png'); $pdf->SetY(35); // call the table creation method $pdf->SetFont('Arial','B',16); $pdf->Cell(0,10,$plateNo); $pdf->SetY(45); $pdf->SetFont('Arial','B',16); $pdf->Cell(0,10,$model); $pdf->SetXY(310, 45); $pdf->SetFont('Arial','B',16); $pdf->Cell(0,10,date("m/d/Y")); $pdf->SetY(55); $pdf->BuildTable($header,$data); $pdf->Output(); ?> Why is FPDF's Output not working? or is something wrong with my browser? I already tried putting paramaters on it but still no go I tried Output('foo.pdf','I') not working but if i itegrate my chrome withIDM it just downloads but when i disable integrationnothing happens.
  4. Hello everyone! I have just finished my first HTML/CSS class, so I have a lot left to learn. One of the unfortunate things that was not covered at all in my class was cross-browser compatability. I made my website where it looked good in Chrome, but had things broken in IE and FireFox. A friend suggested I try converting some of my 'loose html5 coding' to the more strict XHTML. Any feedback or suggestions would be very welcome overall, and specifically checking how this looks across browsers. I'm currently at work where I'm stuck using Win XP with IE7. It looks so broken on IE 7 I wouldn't know where to start. www.rusticspices.com/ (original project) www.rusticspices.com/xhtmltest.html (testing xhtml changes) xhtmltest.html
  5. I have a flash player I made a long time ago, with a long standing issue. The player loads an xml file from the server with song names and mp3s file locations. The problem is that in Chrome (and not in FF for instance), the song names just don't appear in the song list. I remember trying to change the font at the time but nothing seemed to help. The xml is loaded because the songs play, and the list is populated, but you just can't see the names (you can click where they are supposed to be). I'm not sure where the problem is, but I thought this is one of those type of things that you spend hours looking for and can be solved in a minute and yet someone out there must have the answer! Thanks in advance for any suggestions
  6. Hello: how to fix overflow:hidden for chrome and opera...?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.