<?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>311208</bug_id>
          
          <creation_ts>2026-03-31 11:27:56 -0700</creation_ts>
          <short_desc>[WPE] Enable remaining WebKitFaviconDatabase API tests</short_desc>
          <delta_ts>2026-03-31 11:27:56 -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>WPE WebKit</component>
          <version>WebKit Nightly Build</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>296927</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Adrian Perez">aperez</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>bugs-noreply</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2195627</commentid>
    <comment_count>0</comment_count>
    <who name="Adrian Perez">aperez</who>
    <bug_when>2026-03-31 11:27:56 -0700</bug_when>
    <thetext>As per bug #296927 we will be enabling the new favicon API for the WPE port, but making
all the API tests work would be quite a bit of churn because it would entail peppering many
preprocessor guards around, so instead it would be better to rewrite them in a way that the
tests a.) are more robust, as currently they are quite flaky, and b.) we can use helper classes
and methods that have different implementations depending on which build options and port
were enabled to avoid putting preprocessor guards everywhere.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>