<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>116579</bug_id>
          
          <creation_ts>2013-05-21 14:52:30 -0700</creation_ts>
          <short_desc>[Mac] XMLHttpRequest timeout is accounted for incorrectly - should be total time, not inactive time</short_desc>
          <delta_ts>2015-09-04 12:34:06 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>XML</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          <see_also>https://bugs.webkit.org/show_bug.cgi?id=98156</see_also>
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Alexey Proskuryakov">ap</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>d-r</cc>
    
    <cc>youennf</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>892023</commentid>
    <comment_count>0</comment_count>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2013-05-21 14:52:30 -0700</bug_when>
    <thetext>XHR timeout attribute specifies how long the request may take. (At least) the Mac implementation is different, it only triggers a timeout if the connection is idle for this long.

&quot;Can be set to a time in milliseconds. When set to a non-zero value will cause fetching to terminate after the given time has passed.&quot;

&quot;This implies that the timeout attribute can be set while fetching is in progress. If that occurs it will still be measured relative to the start of fetching.&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1123387</commentid>
    <comment_count>1</comment_count>
    <who name="youenn fablet">youennf</who>
    <bug_when>2015-09-04 03:35:06 -0700</bug_when>
    <thetext>This might be covered as part of bug 98156.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1123447</commentid>
    <comment_count>2</comment_count>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2015-09-04 09:10:53 -0700</bug_when>
    <thetext>Sounds like it would be, but only for async requests, not for sync ones.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1123546</commentid>
    <comment_count>3</comment_count>
    <who name="youenn fablet">youennf</who>
    <bug_when>2015-09-04 12:34:06 -0700</bug_when>
    <thetext>(In reply to comment #2)
&gt; Sounds like it would be, but only for async requests, not for sync ones.

Right.
For Soup and CURL, async calls to the underlying libraries are made within a sync loop.
I do not know whether this is actually worth the effort but Mac may use a similar strategy.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>