Content tag parsing fix

[Issue#]       LINUXWRT-438
[Bug]          Bug in content parsing when src == "" is treated as if not encountered at all
[Cause]        Wrong content parswing changes
[Solution]     Fix
[Verification] Run tests:
 wrt-extra-tests-w3c --output=text --regexp='br'
 wrt-extra-tests-w3c --output=text --regexp='bq'
 wrt-extra-tests-w3c --output=text --regexp='bs'
 wrt-extra-tests-w3c --output=text --regexp='d7'
 wrt-extra-tests-w3c --output=text --regexp='d8'
 wrt-extra-tests-w3c --output=text --regexp='gb'
 wrt-extra-tests-w3c --output=text --regexp='b3'
 wrt-extra-tests-misc --output=text --regexp='first_content'
 wrt-extra-tests-misc --output=text --regexp='prefer_tizen_content'

Change-Id: I4d0eb996a4bcebbfab960fbd73c41eb04c124dde

diff --git a/src/configuration_parser/widget_parser.cpp b/src/configuration_parser/widget_parser.cpp
index ddfd2b4..b1e5282 100755 (executable)
--- a/src/configuration_parser/widget_parser.cpp
+++ b/src/configuration_parser/widget_parser.cpp
@@ -724,7 +724,7 @@ class ContentParser : public ElementParser
 
     virtual void Verify()
     {
-        if(!!m_data.startFile)
+        if(!!m_data.startFileEncountered)
         {
             if(m_data.startFileNamespace == m_namespace
                 || m_namespace != ConfigurationNamespace::TizenWebAppNamespaceName)
@@ -734,6 +734,7 @@ class ContentParser : public ElementParser
             //else continue -> if previous item was not in tizen namespace
         }
 
+        m_data.startFileEncountered = true;
         m_data.startFileNamespace = m_namespace;
 
         //we're consciously setting startFile even if m_src is null or invalid.