[
https://issues.apache.org/jira/browse/TRINIDAD-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman resolved TRINIDAD-2027.
Resolution: Fixed
In facelets, pagination of tr:table is broken
[
https://issues.apache.org/jira/browse/TRINIDAD-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992207#comment-12992207
]
Mamallan Uthaman commented on TRINIDAD-2027:
Thanks Andy. I just tried
: Components
Affects Versions: 2.0.0-beta-2
Environment: Any desktop browser
Reporter: Mamallan Uthaman
In a facelet page using Trinidad tags, table's prev and next links are broken.
From a web inspector, I observed that the facelet page's httpRequest contains
source/event
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1922:
---
Resolution: Fixed
Fix Version/s: 2.0.0-beta-2
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986163#action_12986163
]
Mamallan Uthaman commented on TRINIDAD-1819:
Applying the new patch to trunk
+1
-- Mamallan
On 1/14/2011 4:10 AM, Matthias Wessendorf wrote:
+1
On Fri, Jan 14, 2011 at 1:10 PM, Matthias Wessendorf mat...@apache.org wrote:
Hi,
I've created a Trinidad 2.0.0-beta-1 release candidate, with the
following artifacts
up for a vote:
SVN source tag (r1058869):
[
https://issues.apache.org/jira/browse/TRINIDAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1978:
---
Resolution: Fixed
Fix Version/s: (was: 2.0.0.3-core
Hi all,
It would be a great help if someone can review my patch for the issue
TRINIDAD-1978 - Platforms for Android and Palm Browsers Are Not Detected.
Thanks
Mamallan
[
https://issues.apache.org/jira/browse/TRINIDAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1978:
---
Status: Patch Available (was: Reopened)
Platforms for Android and Palm Browsers
Components: Components
Affects Versions: 2.0.0.3-core
Environment: all platforms
Reporter: Mamallan Uthaman
My patch for TRINIDAD-1978 seems to have broken the Trinidad build. While I'm
investigating why my patch has broken the build. I will upload a patch to
revert the TRINIDAD
[
https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1986:
---
Status: Patch Available (was: Open)
Fix for TRINIDAD-1978 Has Broken
[
https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974422#action_12974422
]
Mamallan Uthaman commented on TRINIDAD-1986:
The patch is applicable only
[
https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1986:
---
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman reopened TRINIDAD-1978:
The current patch seems to have broken the Trinidad build, so TRINIDAD-1981 has
[
https://issues.apache.org/jira/browse/TRINIDAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1978:
---
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1933:
---
Resolution: Fixed
Fix Version/s: 1.2.14-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1978:
---
Status: Patch Available (was: Open)
Platforms for Android and Palm Browsers
Components: Components
Affects Versions: 1.2.13-core
Environment: Android Devices
Reporter: Mamallan Uthaman
Priority: Minor
Currently, Trinidad doesn't detect the platform for Android and Palm's Webkit
browsers. We need to change user-agent parsing logic
Hi all,
You are welcome to review my patches for issues below:
TRINIDAD-1933 Handling Windows Mobile 6.5 browser
TRINIDAD-1825 Mobile Browsers - PPR broken in Facelets
Thanks
Mamallan
[
https://issues.apache.org/jira/browse/TRINIDAD-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1933:
---
Status: Patch Available (was: Open)
Handling Windows Mobile 6.5 browser
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918148#action_12918148
]
Mamallan Uthaman commented on TRINIDAD-1922:
@Pavithra: Not sure we are both
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918310#action_12918310
]
Mamallan Uthaman commented on TRINIDAD-1922:
On further investigation, I
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918366#action_12918366
]
Mamallan Uthaman commented on TRINIDAD-1922:
Since developers might use
Versions: 1.2.13-core
Environment: Windows Mobile 6.5
Reporter: Mamallan Uthaman
Priority: Minor
The format of WM 6.5's user-agent string has been changed, so we need to
include a parsing logic to handle this new user-agent.
--
This message is automatically
[
https://issues.apache.org/jira/browse/TRINIDAD-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917038#action_12917038
]
Mamallan Uthaman commented on TRINIDAD-1922:
@Cedric: Sorry, your patch
[
https://issues.apache.org/jira/browse/TRINIDAD-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917067#action_12917067
]
Mamallan Uthaman commented on TRINIDAD-1881:
Myfaces has recently fixed
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917111#action_12917111
]
Mamallan Uthaman commented on TRINIDAD-1825:
Unlike MyFaces, Mojarra
: Components
Affects Versions: 2.0.0.3-core
Environment: Any browser
Reporter: Mamallan Uthaman
Trinidad currently has an issue partial refreshing an tr:inputText. This
problem is specific to facelets where we use JSF Ajax apis. I tested with the latest
code from our trunk, and below
[
https://issues.apache.org/jira/browse/TRINIDAD-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman resolved TRINIDAD-1921.
Resolution: Duplicate
This issue seems to similar to TRINIDAD-1826
JavaScript
[
https://issues.apache.org/jira/browse/TRINIDAD-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12914597#action_12914597
]
Mamallan Uthaman edited comment on TRINIDAD-1921 at 9/24/10 3:12 PM
[
https://issues.apache.org/jira/browse/TRINIDAD-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12914600#action_12914600
]
Mamallan Uthaman commented on TRINIDAD-1826:
We need to apply this patch
Components: Components
Affects Versions: 2.0.0.3-core
Environment: Any browser
Reporter: Mamallan Uthaman
Trinidad currently has an issue partial refreshing an tr:inputText. This
problem is specific to facelets where we use JSF Ajax apis. I tested with the
latest
Affects Versions: 1.2.13-core
Environment: Blackberry 5.0
Reporter: Mamallan Uthaman
I presume the probable cause of the issue is Trinidad is rendering some
JavaScript code which simply crashed the BB's JS engine. We need to further
investigate this issue to narrow
[
https://issues.apache.org/jira/browse/TRINIDAD-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1918:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.2.14-core
Hi all,
I have uploaded a patch (TRINIDAD- 1918) to change the user-agent
parsing logic in Trinidad to recognize Blackberry's Webkit browser. You
are welcome to review the patch.
Thanks
Mamallan
Issue Type: Bug
Components: Components
Affects Versions: 1.2.13-core
Environment: Blackberry 6.0
Reporter: Mamallan Uthaman
Priority: Minor
Trinidad does recognize the request from BB's Webkit browser is from a Webkit
browser
[
https://issues.apache.org/jira/browse/TRINIDAD-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1918:
---
Status: Patch Available (was: Open)
Trinidad Couldn't Recognize the Platform
Hi Jeanne,
I don't foresee any issue with mobile, of course, mobile XSS files do
have a lot of styles rendered specifically for a platform and a
browser. But with new CSS rules like @agent, versions and platform along
with upcoming @import feature, I believe we can successfully convert XSS
Hi Jeanne,
I am referring to the XSS files in Trinidad source code.
Thanks
Mamallan
On 9/13/2010 4:51 PM, Jeanne Waldman wrote:
Hi Mamallan,
Are the mobile XSS files you are referring to the ones in Trinidad src
code or are they external?
Jeanne
mamallan.utha...@oracle.com wrote, On
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman reopened TRINIDAD-1819:
The current patch for this issue is not robust enough to handle other scenarios
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1819:
---
Status: Patch Available (was: Reopened)
PPR Issues in Windows Mobile 6
Hi all,
I have uploaded a patch for the issue TRINIDAD-1819. This patch will fix
the pagination problem in table for Windows Mobile and Blackberry
browsers. Your reviews are welcome.
Thanks
Mamallan
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908274#action_12908274
]
Mamallan Uthaman edited comment on TRINIDAD-1819 at 9/11/10 12:26 AM
[
https://issues.apache.org/jira/browse/TRINIDAD-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1876:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.0.3-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1826:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 2.0.0.3-core
[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898422#action_12898422
]
Mamallan Uthaman commented on MYFACES-2876:
---
I'm sure Windows Mobile will need
Issue Type: Bug
Components: Components
Affects Versions: 2.0.0-alpha
Environment: Blackberry 4.7
Reporter: Mamallan Uthaman
In Blackberry (BB) 4.7, f:ajax works with Mojarra components, but using
f:ajax with Trinidad components simply crashed BB4.7 browser
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896156#action_12896156
]
Mamallan Uthaman edited comment on TRINIDAD-1825 at 8/12/10 3:55 PM
Environment: Windows Mobile 6.1
Reporter: Mamallan Uthaman
In Windows Mobile (WM) 6.1 platform, f:ajax is converted into a full-page
submit instead of a PPR. The reason is unlike Webkit based mobile-browsers, WM
6.1 or Blackberry (BB) 4.6 offers only a limited JavaScript-DOM
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898023#action_12898023
]
Mamallan Uthaman commented on TRINIDAD-1825:
My test results with MyFaces2.0
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898023#action_12898023
]
Mamallan Uthaman edited comment on TRINIDAD-1825 at 8/12/10 10:59 PM
: Components
Affects Versions: 2.0.0-alpha
Environment: Windows Mobile 6.1, Blackberry 4.6
Reporter: Mamallan Uthaman
For JSPX/JSP pages, we still use legacy PPR code, but our PPR response format
has been changed for JSF 2.0. Mobile browsers don't seem to handle this new
PPR
[
https://issues.apache.org/jira/browse/TRINIDAD-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1876:
---
Status: Patch Available (was: Open)
Mobile Browsers - PPR broken in JSPX/JSP
Hi all,
I have upload my patches for the following issues which involves mobile
browsers. Your comments and reviews are welcome.
TRINIDAD-1876: PPR Broken in JSPX/JSP pages
TRINIDAD-1826: Page Navigation Broken in BlackBerry 4.6
Thanks
Mamallan
Hi,
From our Trinidad code (RequestQueue.js), I see we use
jsf.ajax.request() only for Facelets, is this intended behavior? In
other words, in a JSP page, for legacy partialSubmit = true requests,
does Trinidad intend to use jsf.ajax.request() or legacy code?
RequestQueue.js:
/
Thanks Werner.
- Mamallan
On 7/27/2010 1:59 PM, Werner Punz wrote:
Am 27.07.10 22:52, schrieb mamallan.utha...@oracle.com:
Hi,
From our Trinidad code (RequestQueue.js), I see we use
jsf.ajax.request() only for Facelets, is this intended behavior? In
other words, in a JSP page, for legacy
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12892961#action_12892961
]
Mamallan Uthaman commented on TRINIDAD-1825:
I tested my patch with jspx
[
https://issues.apache.org/jira/browse/TRINIDAD-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1826:
---
Status: Patch Available (was: Open)
Page Navigation and PPR Broken
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1825:
---
Status: Patch Available (was: Open)
PPR Broken in Windows Mobile 6
Hi Max,
Sure, I will file a JIRA for this problem.
Thanks
Mamallan
On 7/14/2010 7:33 AM, Max Starets wrote:
Mamallan,
We are not aware of this problem. This seems like a bug in our JSF2
Ajax integration code - we are trying to get PartialViewContextImpl
before FacesContext is initialized
Affects Versions: 2.0.0-alpha
Environment: All platforms
Reporter: Mamallan Uthaman
The dialog framework of Trinidad seems to be broken during JSF2.0 upgrade. You
can reproduce this problem with a basic use-case:
a) Create a main page and a dialog page
b) Set
Hi Max,
I created following JIRA to fix this problem:
https://issues.apache.org/jira/browse/TRINIDAD-1854
Thanks
Mamallan
On 7/14/2010 5:32 PM, mamallan.utha...@oracle.com wrote:
Hi Max,
Sure, I will file a JIRA for this problem.
Thanks
Mamallan
On 7/14/2010 7:33 AM, Max Starets wrote:
Hi all,
Trinidad's dialog framework doesn't seem to work any more in our trunk
(JSF2.0). Is there anybody aware of this issue? if so, can you please
share some detail. My server is WLS 10.3, and I can traverse from main
page to dialog, but following exception occurs when my dialog tries to
[
https://issues.apache.org/jira/browse/TRINIDAD-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1841:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.2.14-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1841:
---
Status: Patch Available (was: Open)
CommandButton Not Supporting Onfocus
[
https://issues.apache.org/jira/browse/TRINIDAD-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1831:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.2.14-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1832:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.2.14-core
Components: Components
Affects Versions: 1.2.13-core
Environment: all platforms
Reporter: Mamallan Uthaman
Priority: Minor
Trinidad's commandButton doesn't provide any attribute to handle onfocus or
onblur event. I propose to introduce onfocus and onblur
[
https://issues.apache.org/jira/browse/TRINIDAD-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1831:
---
Status: Patch Available (was: Open)
Design Time Metadata Missing for a Few
[
https://issues.apache.org/jira/browse/TRINIDAD-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1832:
---
Status: Patch Available (was: Open)
In BlackBerry 4.7, Partial Refreshing
Hi all,
I have uploaded patches for issues below, and you are welcome to review
these patches.
TRINIDAD-1832In BlackBerry 4.7, Partial Refreshing an Empty
Table breaks Page Navigation
TRINIDAD-1831Design Time Metadata Missing for a Few Trinidad
Components
Thanks
Mamallan
Components: Components
Affects Versions: 1.2.13-core
Environment: JDeveloper 11g
Reporter: Mamallan Uthaman
Priority: Minor
Currently, Trinidad provided a design-time metadata to identity whether a
component's attribute is translatable
Components: Components
Affects Versions: 1.2.13-core
Environment: BlackBerry 4.7
Reporter: Mamallan Uthaman
Priority: Minor
In cases where we partial refresh an empty table with some rows,
page-navigation links and detailStamp facet's links (Show/Hide
[
https://issues.apache.org/jira/browse/TRINIDAD-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12876853#action_12876853
]
Mamallan Uthaman commented on TRINIDAD-1825:
There could be many other
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1819:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 1.2.14-core
-alpha-2
Environment: Windows Mobile 6
Reporter: Mamallan Uthaman
Currently, PPR in Windows Mobile 6 neither performs a partial submit nor a
full-page submit. I guess, for mobile browsers, we need to revert the PPR
handling to old legacy way than JSF2 APIs.
--
This message
: Components
Affects Versions: 2.0.0-alpha-2
Environment: BlackBerry 4.6
Reporter: Mamallan Uthaman
Page navigation and PPR have stopped working in BlackBerry browsers of
versions 4.6 and above. It is likely that JSF2 Ajax change has broken these
functionality
Hi all,
I have uploaded a patch (TRINIDAD- 1819) for handling PPR issues in
Windows Mobile 6. You are welcome to review the patch.
Thanks
Mamallan
: 1.2.12-core
Environment: Windows Mobile 6
Reporter: Mamallan Uthaman
Priority: Minor
In cases where we partial refresh an empty table with some rows, page
navigation in a table component ceases to work. Also, partial refresh of
inputText simply add another inputText
[
https://issues.apache.org/jira/browse/TRINIDAD-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1819:
---
Status: Patch Available (was: Open)
PPR Issues in Windows Mobile 6
This is in regard with how Trinidad handle JavaScript free fallback
during mobile rendering. Basically, we assign the JavaScript capability
for a few mobile user-agents to 'none' in their capability files
(Trinidad maintains a capability file for each user-agent). The method
supportsScripting
[
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834611#action_12834611
]
Mamallan Uthaman edited comment on TRINIDAD-1728 at 2/26/10 3:04 AM
[
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1728:
---
Resolution: Fixed
Fix Version/s: 1.2.14-core
Status: Resolved
URL: https://issues.apache.org/jira/browse/TRINIDAD-1728
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 1.2.13-core
Environment: HTC Opera Mobile
Reporter: Mamallan Uthaman
Priority: Minor
Affects Versions: 1.2.13-core
Environment: HTC Opera Mobile
Reporter: Mamallan Uthaman
Priority: Minor
Trinidad is not handling requests from Opera Mobile running in HTC. The reason
is current user-agent parsing logic for Opera mobile cannot handle requests
[
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1728:
---
Status: Patch Available (was: Open)
Trinidad not supporting Opera Mobile in HTC
[
https://issues.apache.org/jira/browse/TRINIDAD-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834611#action_12834611
]
Mamallan Uthaman edited comment on TRINIDAD-1728 at 2/17/10 2:32 AM
Hi all,
I have uploaded a patch (TRINIDAD- 1728) for handling Opera-Mobile
browser that runs in HTC device. You are welcome to review the patch.
Thanks
Mamallan
Hi Andrew,
Mobile browsers provide very limited support for JavaScript, and the
level of support varies widely. Hence, unless jsf.ajax.request specially
handles limitations of a mobile browser, using jsf.ajax.request probably
won't work in mobile browsers. So to preserve PPR support, for
[
https://issues.apache.org/jira/browse/TRINIDAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1619:
---
Resolution: Fixed
Fix Version/s: 1.2.14-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1617:
---
Resolution: Fixed
Fix Version/s: 1.2.13-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1616:
---
Resolution: Fixed
Fix Version/s: 1.2.13-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1618:
---
Resolution: Fixed
Fix Version/s: 1.2.13-core
Status: Resolved
[
https://issues.apache.org/jira/browse/TRINIDAD-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12803425#action_12803425
]
Mamallan Uthaman commented on TRINIDAD-1616:
The uploaded patch also applies
[
https://issues.apache.org/jira/browse/TRINIDAD-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12803426#action_12803426
]
Mamallan Uthaman commented on TRINIDAD-1617:
The uploaded patch also applies
[
https://issues.apache.org/jira/browse/TRINIDAD-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12803433#action_12803433
]
Mamallan Uthaman commented on TRINIDAD-1618:
TRINIDAD-1618.patch also
[
https://issues.apache.org/jira/browse/TRINIDAD-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamallan Uthaman updated TRINIDAD-1562:
---
Resolution: Fixed
Fix Version/s: 1.2.13-core
Status: Resolved
Hi all,
I have a few patches that need to be reviewed before I can commit it.
All but one patches are related to mobile development:
TRINIDAD-1619 - This patch applies to both desktop as well as mobile.
The issue is a column's width is not rendered when all the columns of a
table have empty
+1
- Mamallan
Blake Sullivan wrote:
+1
-- Blake Sullivan
Matthias Wessendorf said the following On 1/13/2010 9:19 AM PT:
On Wed, Jan 13, 2010 at 6:14 PM, Matt Cooper mcoo...@apache.org wrote:
Rather than having the casablanca skin as a separate jar file, I would
prefer to see it
It looks fantastic, thanks for your great work Catalin.
-Mamallan
Jakob Korherr wrote:
Really great work, guys!
2010/1/8 Matthias Wessendorf mat...@apache.org
mailto:mat...@apache.org
some more technical discussions on the HOW to apply the new
awesome skin:
1 - 100 of 208 matches
Mail list logo
