Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] getElementById

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] getElementById
 Login/Join
 
Håkan
Guru
posted
All,

I came across this writing on Tech Support, and I'm wondering what you guys make out of it. Are IB implying they are in the process of dropping support for W3C standards and implementing legacy functions?

However in WebFOCUS 7.7.xx and higher, there are exposed functions the HTML
Composer makes available for the developer to use. The function:
IbComposer_enableHtmlElement('ElementID', true/false);

This function would accomplish the same effect as the above code and should be
used if the developer is using WebFOCUS 7.7.xx or higher:
Change: document.getElementById('agency_code').disabled = false;
To: IbComposer_enableHtmlElement('agency_code',false);

The exposed functions will always work when a new release is available.

Any thoughts?

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
Wep5622
Virtuoso
posted Hide Post
quote:
Change: document.getElementById('agency_code').disabled = false;
To: IbComposer_enableHtmlElement('agency_code',false);


Gosh, that's not even correct! The second statement does the opposite of the first...

Anyway, getElementById() will always work, regardless of what IBI says. Personally, I would probably use JQuery's $('#agency_code').prop('disabled', false) instead.

The difference is that IBI's implementation does a couple of things for controls they customized, such as comboboxes and arrays of checkboxes or radio buttons. It also behaves a bit differently for Internet Explorer, I think that has to do with old versions (6 or 7 and older).

I do think it's bad design that HTML uses a property disabled=true instead of enabled=false; inverse logic is confusing. BTW, Microsoft does the same in the Advanced Internet Explorer options - it's a common ailment.

This message has been edited. Last edited by: Wep5622,


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Håkan
Guru
posted Hide Post
I agree, inverse logic is confusing. Anyway, I think I stick to the HTML/Javascript DOM style.

Regards
Håkan


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
David Glick
Guru
posted Hide Post
If you don't use our API functions, your code may not work in newer releases and Support will tell you to change to the API functions at that point.


David Glick
Director WebFOCUS App Studio
and WebFOCUS Developer Studio
WebFOCUS Division
Information Builders, Inc.
Direct (917) 339-5560
Voice Mail (212) 736-6250 x3560
Fax (212) 947-5168
Email david_glick@ibi.com
 
Posts: 315 | Registered: April 13, 2004Report This Post
Håkan
Guru
posted Hide Post
David, is there ANY kind of documentation on your legacy API functions?


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
David Glick
Guru
posted Hide Post
They are not "legacy" API functions. They are documented in the manual like everything else...


David Glick
Director WebFOCUS App Studio
and WebFOCUS Developer Studio
WebFOCUS Division
Information Builders, Inc.
Direct (917) 339-5560
Voice Mail (212) 736-6250 x3560
Fax (212) 947-5168
Email david_glick@ibi.com
 
Posts: 315 | Registered: April 13, 2004Report This Post
Håkan
Guru
posted Hide Post
David,

sorry had not seen that section on the 8.08 documentation site.

Regards
Håkan


WebFOCUS DS 8.0.06/08 DS/AS
WebFOCUS RS 8.0.08 (Linux/IBM i)
WebFOCUS Client 8.0.06 (Linux)
 
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] getElementById

Copyright © 1996-2020 Information Builders